Platform 8.8.20

release date: march 19, 2024

New features

Alerts: triggered alert details window

A new details window has been created, accessible by clicking on an alert’s ID. Here you can easily view all the details of a triggered alert at a glance and have full control over its management. Learn more here.

Open

Open

Alerts: search triggered alerts by ID

A new way of searching alerts by ID has been implemented, which will help you find exactly the alert you’re looking for. Learn more here.

Alerts: type field in grouped triggered alerts

The type field when grouping triggered alerts have been updated to reflect the triggering method used for the alert definition. Learn more here.

Alerts: alert auditing

We’ve created a new data table that register all the activity related to triggered alerts during their lifecycles, the devo.audit.alert.triggered table. Learn more here.

We’ve added a new json field to the devo.audit.alert.definition table, which includes information about changes performed in alert definitions during their lifecycles. Learn more here.

Bug fixing

Alerts

1. Alert creation/cloning fails when Alerts running limit is reached.
   The behavior has been fixed, and alerts are created and cloned as disabled when they exceed the limit.

2. Error when clicking Go to query on a pre-defined monitoring alert.
   The behavior has been fixed, and now the option is disabled for this kind of alerts.

Flow

1. Some alerts were duplicated when installing the new version of Flow, as the query retrieved information from deprecated fields.
   Now the information is retrieved from the correct fields and alerts are no longer duplicated.

2. Some DevoSource cursors were missing after installing the new version of Flow, as alert generation
   recovery didn’t work for several-type alerts.
   Cursors are now correctly written for this type of alerts.

3. Unexpected null value on the creation date field.
   Now it shows the correct value.

4. DevoSource recovery process generates duplicated alerts and events when the date of the last written cursor is significantly distant in the past.
   To fix this, DevoSource now includes a check during startup to retrieve from the cache only those cursors that do not exceed a certain number of days or grouping periods.

5. DevoSource queries that involve grouping periods use a different alignment than the internal component for query processing (first day of the current year vs. first epoch time). This misalignment can result in partial results for each initial period during every restart, depending on the stored cursors.
   Grouping periods are now aligned using the same benchmarks to prevent result alterations.