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.
Our GitHub integration unlocks a lot of new functionality in OpsLevel:
- New checks are available that can dive deep into your codebase.
Do you want to make sure all your Python services are on a modern version of the language? Or that no services are using an old library that you’re trying to deprecate? Or that every service has a CircleCI config file? You can do that.
- OpsLevel will stay up-to-date by reading the opslevel.yml files in your services’ repos.
Now you don’t have to go to OpsLevel’s UI to update your service metadata and can make changes to service metadata using pull requests.
To set up a GitHub or Bitbucket integration, go to our Integrations tab and hit “New Integration”. Then, look for the integration you want and hit “Add Integration.”
Follow the prompts, tie it to your organization and OpsLevel will soon show you a list of all repositories it has access to.
Map a Repository to a Service
For the Repo-specific features to work, OpsLevel needs to know which services map to which repos.
If you’ve added an opslevel.yml file to your repo, it will automatically create a service in OpsLevel and do the mapping for you. You can skip the below.
But if you have already created a service in OpsLevel, then you should manually map it to a specific repo. To do this, simply add a link to your repo in that service’s Operations Center.
If found, OpsLevel will show a green pill indicating that the service is connected and that it is actively monitoring that repo.
(Note: if you have a mono-repo, just add a link directly to the subfolder that represents your service.)
If you have any questions or are interested in trying out OpsLevel, hit us up at firstname.lastname@example.org.