Catalog

Services and repositories come in many shapes and sizes. You can fully extend OpsLevel’s data model to fit your needs by tagging your services and repositories with key/value pairs. With our Tags feature, OpsLevel can track additional or custom attributes, as well as allow you to search and filter by these attributes.

OpsLevel is your one-stop shop for understanding the microservices you have running in your architecture. A key component to understanding your microservices is to actually see what code is running in production, and when/how that changes.

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

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 GitLab application. You will be notified by OpsLevel when there is an update to the OpsLevel GitLab application available.