RELEASE DATE: SEPTEMBER 9, 2024
New features
Alerts: auditing new triggered alerts
New triggered alerts are now registered in the devo.audit.alert.triggered table, providing reference not only for the changes that alerts undergo but also for their creation. Learn more here.
Alerts: filter presets for triggered alerts
Filters and time ranges can now be saved as presets to be later applied, suppressing the need of applying the same filters repeatedly and speeding up the filtering process. Learn more here.
Alerts: filter by domain in Multitenant structures
Thanks to this new filter and the dedicated column in the triggered alerts page, admins can easily contextualize alerts for a more accurate analysis when it comes to multitenant structures. Learn more here.
Alerts: go to query filtered by key (several, inactivity, gradient)
When using the Go to query option to access the data table, it now displays the specific data that present the anomaly and caused the alert to trigger. This is achieved by means of filtering by the specific key, and applies to several, inactivity, and gradient types. Learn more here.
Bug fixes
Alerts: even though previously applied filters are successfully reapplied when returning to the triggered alerts area from other parts of the Devo platform, the URL parameters that reflect those filters are dropped out.
Alerts: using a URL with invalid parameters leads to an error in the page. This error is prevented by ignoring the invalid parameter and executing only the recognized ones.
Alerts: when there’s an existing post-filter, the edit menu does not allow to create a new one.
Alerts: some delivery methods do not work with alerts definitions that do no have a summary or description.
Alerts API: inability to parse alert date when dispatching alerts with less than 3 milliseconds digits.
Vulnerability fixes have been updated for alerts and flow.