June at OpsLevel saw the release of Catalog Engine, a bundle of features created to assist users to get up and running with an actionable catalog fast. Plus new features and integrations for increased visibility and security.

Bigs:

Catalog Engine is here!

OpsLevel is excited to announce Catalog Engine! Catalog Engine is a bundled set of automated, AI-enhanced features that support fast, accurate catalog creation and lightweight, continuous maintenance.

Catalog Engine includes:

• Automated catalog creation
• Recommended service owners
• Grouping by aliases
• Service page actions
• AI-derived service page descriptions

You’ve probably heard of these features as they’ve been rolled out individually over the last few months and now is a great time to start incorporating the Catalog Engine feature set into your workflows. You can learn more on the new Catalog Engine page, in the guidebook, or watch the video.

Automatically collect, track, and view package versions

Users now have more visibility into packages and their versions. We automatically gather package and package version data daily from all git forge integrations. This new feature also includes the ability to identify package versions for dependencies of dependencies, an important factor when searching for vulnerabilities found in your software supply chain. 

By creating a check against package versions, teams can identify which services could be impacted, prioritize affected package versions for remediation, and track progress through a centralized campaign. Learn more about how it works in our docs. 

Azure Integration

OpsLevel now integrates with Microsoft Azure Resources for infrastructure. This pull-based integration allows you to import Infrastructure Objects across your various Azure accounts. Once imported, you can see details about your objects (Resource IDs, source account, region, storage size, etc), filter across Azure accounts ("how many databases do I have cumulatively across all my accounts?"), and define relationships between infrastructure objects to Services, Systems, and other Infrastructure Objects.

For more information, see our docs. 

New Team Member Role

We're excited to announce the launch of a new Role-Based Access Control (RBAC) feature: the Team Member role. This addition is designed to enhance team collaboration and streamline service management while ensuring robust security and control.

The Team Member role in OpsLevel merges ownership information from the catalog into the authorization system. Here's how it works:

• On a Team That Owns a Service? You can edit it.
• Not on a Team That Owns a Service? You can’t edit it.

This authorization scheme respects the recursive nature of teams. By default, users provisioned through SCIM or SSO will receive the role of Team Member. Admins can modify the default role for their account in the Roles & Permissions section of the OpsLevel platform. Read more on our blog.

‍Smalls:

• Detected Services drawer to help federate service suggestion management can now be enabled in Admin Settings.
• Service templates now support human-readable prompts, booleans, integers, and non-standard JSON objects.
• CSV export is now available for the repositories list page.
• Users now have the option to disable "just in time" user creation for SSO.
• Users can now allow email updates via SCIM.

‍