Nobl9 application (1.135.0)
- Alert Method details with dedicated pages
- Budget Adjustment events retained after SLO updates
- Corrected SCIM API error handling
- Fixed certain API Responses type
Release details
new No data anomaly annotation
It is crucial to be notified if your SLO reports no data. Nobl9 has already been providing notifications for no-data events through its supported alert methods, assuming data anomaly notifications are configured for your SLO. The only record of such no-data incidents resided within these notifications.
Now, however, Nobl9 directly annotates no-data periods on your SLO charts, making them readily available for retrospective analysis.
Consistent with other annotation types, no-data anomaly annotations are also displayed within the Events section, where a dedicated No data anomaly filter is available under the Annotation type block.
This enhancement allows for better tracking and informed analysis of your SLO's historical performance.
new Search within Global Annotations List filters
Filters in the Global Annotations List: such as Project, Service, or SLO, now include a built-in search feature.
Instead of scrolling through extensive filter lists, simply type to quickly narrow down and select the exact value you're looking for. This streamlines navigation and significantly speeds up the filtering process.
improved Alert Method details with dedicated pages
Alert methods now have their own full-page details views with unique deep links, making navigation clearer and configuration easier than ever.
improved Budget Adjustment events retained after SLO updates
Previously, modifying an SLO's configuration, such as updating the target, could cause the loss of earlier budget adjustment events. Now, historical events are properly retained and persist across changes, ensuring accurate chart displays and correct data accounting during replays.
improved Corrected SCIM API error handling
Fixed incorrect API responses for SCIM requests when referencing user or group resources no longer available in Nobl9. Now, the API returns accurate responses and appropriate status codes.
improved Fixed certain API Responses type
Fixed an issue where certain API endpoints previously returned responses without correctly specifying Content-Type. Now, responses consistently include the application/json header, ensuring reliable API consumption.