Resources

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.

OpsLevel just completed its inaugural HackDays and company getaway. We all piled into a few cars and drove up to a beautiful cottage near Parry Sound, Ontario. Surrounded by some of Canada’s best scenery of trees, lakes, and trails, we first set about for 24 hours of programming. Given our geography, we thought about calling the event “Hack the North”, but that name is taken, so “OpsLevel HackDays” it is.

At OpsLevel, we’re big fans of the 2015 MacBook Pro. The newer 2019 MacBook Pro has some great features like Touch ID, 32 GB RAM, and USB-C power delivery that you can plug on either side. Unfortunately, it also suffers from a failure prone butterfly keyboard design and the dreaded Touchbar. The 2015 MacBook Pro was the last model manufactured by Apple before the switch to Touchbar and and the butterfly keyboard.

OpsLevel is a fantastic source of truth for all of the information around the microservices in your architecture, including all the tools you use to operate each of your microservices. But it’s not always the easiest to find and discover this information when you really need it - say during a major incident, or during a gameday.

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.

Hey friends, Thank you all for the feedback you’ve provided so far. We’ve actioned a lot of the items you’ve given us. Here’s a list of recent changes in this last week: On the Services index page, you can filter by Owner. Filter is stored in the query string so you can share these URLs. You can create a new team inline while creating a new service. This speeds up setting up new services that don’t have associated teams defined yet. UX issue: some users inadvertently logged out because they engaged the profile menu in the top right by hovering over it. We’ve changed the affordance to require a click instead of a hover. UX improvements around inviting users: After inviting a new user, we now clear out the name/email text boxes. Validations don’t scream at you while you type (edited)

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.

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.

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.