February was a big month at OpsLevel! We released a number of features to provide more context and help you prioritize action items.
Larges
🌟 Service Level Change Notifications
Teams can now opt to receive notifications via Slack when service levels change.
Enable notifications to alert teams quickly when a change occurs to a service level. Whether the change is a level up or a level down, teams can now receive notifications through a default Slack channel. Links to the maturity reports of each affected service are provided so teams can immediately assess any potential issues or incidents. This is particularly useful for teams who gate deployments based on service levels.
- Alert entire teams at once, in one place.
- Quick notification of potential issues without having to context switch.
- Faster time to resolution of incidents.
- See the positive effects of changes that influence service maturity.
- Select the right Slack channel for notifications in your team’s page
Mediums
⏳ Service Level Changes Over Time
The Level Progress trend chart now displays which services have changed levels over time. This enables users to see how certain services have either improved or declined over an extended period to form a better overall assessment on the service’s performance. For example, if you're seeing a particular service has had a lot of fluctuation over time that's probably something that should be monitored more closely than other services and investigated.
☑️ Improved Check Labeling
We have updated check labels to provide more context.
Users can now view whether a particular check comes from the rubric or scorecard and if that check affects the overall service maturity. This additional granularity in the information provided with checks enables users to better understand which failed checks should be prioritized for remediation.
📊 Updated Scorecards
A few months ago we made some updates to Scorecards so you can build a set of checks scoped to a specific team, group, category, or anything you want—separate from the Rubric.
Users have always been able to scope checks however through using Filters. Now we’ve made it even easier to use Scorecards to take things one step further, giving you total flexibility to build your Service Maturity program based on the unique needs of your team and organization.
🔆 Highlighting checks that are causing low service levels
For admins: On the Rubric page, we're now highlighting up to three checks that are causing services to fail your lowest service level. For each check, there are several recommended actions to help your service owners succeed.
These suggestions are currently shown to admins only. To dismiss, snooze all suggestions.
👁️ Descriptions for Detected Services
Users can now add descriptions to detected services. This enables users to provide and have access to more granular information regarding newly detected services before making any changes.
✏️ Single Sign-on with Microsoft Entra ID - Docs
OpsLevel provides access through Microsoft Entra ID SSO (previously the Azure Active Directory) for authentication. This method streamlines login access and makes OpsLevel compliance-ready for internal SSO standards set by individual organizations requiring Microsoft Entra ID for authentication. Detailed documentation for the configuration is now available.
Smalls
- Campaign reminder editing now displays the next notification time.
- The sidebar of the Maturity report tab on the service page now allows for filtering.
- Non-self-hosted users now have access to feature management.
- Added the ability to specify custom certificate CA.
Bugfixes
- Table pagination no longer takes multiple clicks when the table is unsorted.
- Templates can now be imported from Bitbucket repos for service creation.
- When configuring a scorecard, users will now be prompted to add a filter. This prevents the Scorecard from inadvertently being applied to every service globally.
- An issue was fixed that caused incorrect services to be displayed on the Scorecard edit page.