Document toolboxDocument toolbox

Platform 8.9.15

Owned by Borja Moro Moreno
Last updated: May 14, 2024
2 min read

release date: may 6, 2024

[ 1 New features ] [ 2 Improvements ] [ 3 Bug fixing ]

New features

Alerts: annotation operations

User can now reply to existing annotations, as well as edit and delete their own annotations. Learn more here.

2024-04-26_13-25-44-20240426-113536.png

Alerts: auditing annotation operations

The actions concerning annotations are now audited and included in the devo.audit.alert.triggered table. Learn more here.

Alerts: rolling & each restrictions

A restriction has been implemented for rolling-type alerts, as well as each-type alerts with subqueries, to prevent excessively frequent queries over short periods. The ratio between period and frequency cannot exceed 120. Learn more here (each) and here (rolling).

Alerts: more info included in the alert details window

The alerts details window in the triggered alerts area now shows the timezone and the specific settings corresponding to the triggering method used when configured. Learn more here.

2024-05-07_11-30-20-20240507-093925.png

Improvements

Alerts: filter by name

The name filter in the triggered alerts page has been enhanced. Rather than having to type names without knowing if they actually exist, it now includes a multi-selection dropdown containing all available options. This results in a more efficient and user-friendly experience. Learn more here.

Bug fixing

Alerts

  1. Error fixed when locale or timezone are nulls from request.

  2. Alert creation in bulk when exceeding the limit has been resolved. Previously, none of these alerts were created, but now all alerts are successfully created with those surpassing the limit being deactivated.

  3. Error fixed when creating an empty annotation though the annotations tab of the alert details page.

  4. Error fixed when trying to create or update an alert that shares the same name with a context in Flow.

Alerts API

  1. Error fixed with alert name being returned as null when defaultParams is null.

  2. Alert bulk installation is successfully completed for the rest of the alerts when encountering an error in one of them.

Flow

  1. Accept HTTP codes greater than 599 and improver error explanation.

  2. Transform queries to rename unnamed fields.

  3. When a DevoSource contains a subquery or has batches enabled shouldn't work with partial data (wrong behavior about alerts with subqueries).

  4. Refactor resource for alert sender last retry. Use syslog url instead of logger and extract address generation for syslog url.

Â