Product

So, OpsLevel is cool and all, but you know what’s not cool? Clicking around in a UI whenever you want to change some of the properties of a service. Well click no longer! Now, with our Git Repository Integration, all you need to do is to plunk down an opslevel.yml file at the root of one of your repositories and OpsLevel will use that to populate the corresponding service on OpsLevel’s side. (If the repository isn’t already mapped to a service, OpsLevel will create a new one.)

With our Git Repository integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Previously, we’ve shown you a Repo File Check, which can be used to verify that a given file exists in your repo, or verify that it contains some specific text.

After setting up a Git Repository Integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Along with the integration comes two new checks: the Repo File Check and the Repo Search Check.

You likely use a myriad of cloud-based tools to operate your services. At OpsLevel, part of our master plan is bringing various data points from all of these tools to help you gain insights and build more reliable software. We’re proud to announce our latest step on this journey with our new Github and Bitbucket integrations.

OpsLevel has become a lot more powerful with the addition of our newest features: Checks and Checklists. Now you can actually codify your best-practices around building and operating microservices and then view how these practices are being followed across your entire architecture.

OpsLevel has a feature where it allows you to define what “tier” each of your services are. This feature has started some good conversations and encouraged many of our alpha users to ask themselves: “What tier are our services, anyway? And what’s in a tier, really?”

We here at Team OpsLevel have been busy and are proud to announce our newest feature: reports. With reports, it’s easy to see the health of your teams and services at a glance.

A modern software catalog must be automatically kept up-to-date to reduce the burden on developers and build trust. The OpsLevel Catalog Engine is an always-on way to create and maintain an accurate catalog rich with metadata. Read on to learn more.

As part of new feature rollouts at OpsLevel, we may occasionally request new permissions for the OpsLevel GitHub application. After that, you will receive a notification via email, and visible in the Installed GitHub applications listing for your organization, requesting you accept the updated permissions. A note will be attached to the notification informing you why we are requesting the changes.