Checks and Checklists

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.


A checklist is, obviously, a list of checks.  But a checklist also comes with “conditions”:  these let you define which of your services this checklist should apply to based on those services’ properties.

There are a number of different checks you can define and most have a lot of options.  You can define a simple ownership check (to make sure none of your services are orphaned), or you can set up tool checks - that make sure your services are using certain operational tools.  You can set up checks that dive into your codebase with our Git Repository integration, or create Manual or Custom Checks.  Go ahead and create some!

Checklist Screenshot

When you have checklists defined with various checks, you can see - on your services’ detail pages - whether these checks are passing or failing for each of the particular services they apply.

You can also get a view of your operational health across all your services with our reports feature.  Moving to Kubernetes?  Below is an example report showing all the services passing and failing a Kubernetes tool check.

More info can be found in our docs section.

Feedback welcome

As always, if you have any feedback about reports, please email us at

Learn how to grow your microservice architecture without the chaos.

Not ready for a demo? Stay in the loop with our newsletter.