Nobl9 application (1.135.0)
Release details
new No data anomaly annotations
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 Filter search in the Events list
The Project, Service, SLO, and User filters in the Events list now include the search functionality.
Instead of scrolling through extensive filter lists, start typing to narrow down the selection and select the exact value you're looking for. This streamlines navigation and significantly speeds up the filtering process.
improved Alert method details page
Alert methods now have their own full-page details views. You can view resources connected to your alert method and share the link to it.
improved Budget adjustment events retained after SLO updates
Budget adjustment events are now preserved even when an SLO is modified. This prevents the previous loss of historical data, ensuring chart accuracy and correct data accounting during replays.
fixed Corrected SCIM API error handling
Fixed incorrect API responses for SCIM requests when referencing user or group resources that are no longer available in Nobl9. Now, the API returns accurate responses and appropriate status codes.
fixed Fixed API endpoint responses
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.