Nobl9 Application (1.57)
- RBAC groups: Group details screen
- Bad over total metrics for AppDynamics
- Formatting of email alerts notifications
- “Lasts for” parameter in the Remaining error budget alert policy condition
Release details
new RBAC groups—additions
We’ve made several additions to RBAC groups, and now there's a Group details screen that shows an overview of important information:
- Users (the list of users associated with the group)
- Group Organization Roles (the specific organization roles assigned to the group)
- Group Project Roles (the specific project roles assigned to the group)
We've also made some improvements to our user list. Now, you can quickly find users based on their organization and project roles. On top of that, we've also added information about user permissions from their respective groups for easier management. Plus, we’ve made it easier to see where users' permissions are coming from by updating the way groups are displayed on the list.
Currently, groups are only available for customers using SCIM integration. Go to Groups documentation to learn more.
new Bad over total for AppDynamics
When it comes to objectives (SLOs), the usual approach is to calculate the ratio of good events to the total number of events. Sometimes, it's hard to automatically determine what counts as a good event, especially when dealing with metrics like error rates in AppDynamics SLOs.
In these cases, it can be challenging to determine what constitutes a good event. Due to this limitation, we've improved the AppDynamics integration, enabling the creation of SLOs that are based on the ratio of bad events to total events.
improved Formatting of email alerts
Our email alert notifications now have a new format that simplifies taking actionable next steps based on the alerts:
improved “Lasts for” parameter in the “Remaining Error Budget” condition
To ensure consistency between the UI and sloctl, we’ve improved the Alert policy wizard for the Remaining Error Budget condition. Now, you can set the Lasts for parameter, that defines for how long alert conditions must persist before triggering an alert.
