May Release Notes

As your system is continuously evolving and changing, your catalog needs to change and evolve with it and that process should be as lightweight as possible. This month at OpsLevel we released several new features to help assist teams with that maintenance, and more.

Bigs

Service recommendation notifications

OpsLevel now has the ability to automatically notify recommended owners when new services are discovered so they can accept or assign ownership. Previously, OpsLevel released the ability to surface recommended owners in the product when a new service is discovered. Now, teams and individuals who have been identified as potential owners will receive an email notification alerting them that there is an action to take so nothing slips under the radar and services aren’t left unmanaged. This new ability greatly helps teams stay on top of their catalog maintenance, making it as seamless as possible, even if they are not in the product on a regular basis. 

Mediums

More intuitive notifications

Service level change notifications in Slack now tell you what check(s) failed so users know exactly what they’ll need to fix and bring those levels back up.

More language support for detected services

OpsLevel can now detect services written in C# on the .NET framework. OpsLevel automatically finds services through your integrations. With this new update, we are expanding on the sources that you can receive that data from, further ensuring the completeness and accuracy of your catalog. 

Run checks on packages directly in OpsLevel

Users now have the ability to automatically collect package version information and run checks on packages. OpsLevel now pulls package information directly from your integrated repositories - this functionality is controlled via settings on each source control integration. Running checks against packages is important to confirm the presence of certain packages and their versions especially in the event of a newly discovered vulnerability. (This is being rolled out incrementally to all customers.)

View all RBAC roles and permissions

All OpsLevel users can now view a table outlining RBAC roles and permissions in the UI. This informs users of their own access level so they have a clear view of their abilities in the product.

‍

Improved communication for service templates

When creating or editing a service template, users can now specify a comment that will be automatically added to the merge request (/ pull request) created for new repos. Customers can use this to communicate any pertinent information such as next steps, etc. for whomever created the new repo/service.

‍

Smalls:

• Users can now download a CSV export of Scorecard data and Infrastructure list.
• The defaultServiceRepository field was added to the services API for fetching a service’s primary repository. 
• The Custom Event Integration endpoint now allows up to fifty Custom Event Checks to be associated with it. 
• Package version checks can now address multiple packages at the same time, using regular expressions.
• The “Teams” filter on the suggested services page now includes suggested owners in the results.
• Service Dependencies page respects service write scope
• Campaigns linked from team pages are default grouped by team
• Weekly e-mail no longer shows “0 services” if there are no services in scope

‍

‍

‍

‍