Integration

Embracing a microservice architecture typically also means deploying much more frequently, which can seem scary. But favoring many incremental deploys is actually a sound risk mitigation strategy since changes tend to be smaller and more isolated.

A service catalog is a valuable asset for any growing engineering organization delivering software at scale. But valuable assets aren’t created or earned easily. That’s why, at OpsLevel, we’re always thinking about ways to make building and maintaining an up-to-date service catalog simpler. Recently we upgraded our Discovered Services capabilities to do just that.

Today, Kubernetes is the de facto standard for container orchestration, running in approximately half of all containerized environments. Platform and infrastructure teams of all shapes and sizes are accustomed to operating Kubernetes in order to run their organizations’ microservices (and applications) at any scale.

Enabling Service Ownership is our north star at OpsLevel. We believe that true service ownership is the future of DevOps and a key to building agile, efficient engineering teams. As a part of making service ownership a reality, we’ve recognized that teams own services, not people. But of course, when you need to get something done urgently, you want to talk to a person, not a team. That’s why OpsLevel now supports tracking functional team membership alongside core service metadata.

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.)

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.

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.

As part of new feature rollouts at OpsLevel, we may occasionally request new permissions for the OpsLevel GitLab application. You will be notified by OpsLevel when there is an update to the OpsLevel GitLab application available.