Obcerv Apps 2.x Release Notes

Overview

Obcerv apps release notes contain the list of new features and known issues in Obcerv apps.

For the latest highlights, see What’s New in Obcerv.

Before you install Obcerv apps, make sure to review the Obcerv Compatibility Matrix. For details on installation, administration, and usage, you may refer to Obcerv Documentation.

To learn more about Obcerv, visit the Obcerv product page.

Obcerv Notifications

Obcerv Notifications 2.1.0

Released: 31 July 2023

New features and enhancements

These are the new features and enhancements of this release:

Issue key Release description
OBAN-210 The Slack test connection now checks whether the channel’s name is configured instead of its ID. This prevents an error previously encountered when only the channel name was supplied and it did not match the channel ID.
OBAN-216 ServiceNow is now available as a notification target.
  • When notifications are triggered, a new ServiceNow incident is created. The affected entities are tagged with the notification-url attribute that contains a permalink to the ServiceNow incident.
  • While the notification is active, reminders are sent as comments to the existing incidents.
  • When the notification is cleared, a final comment is posted to the incident.
  • When the entity or group gets triggered again, a new incident will be created.
OBAN-221 Placeholders are now supported in ServiceNow incident table field values.
OBAN-222 The following placeholders are now supported:
  • ${entity.attribute[<attribute name>]}
  • ${entity.dimension[<dimension key>]}
  • ${group[<group name>]}
OBAN-235 The following self-monitoring data are now available:
  • Notification Failed At: A metric that contains the timestamp of the most recent notification failure.
  • Notification Succeeded At: A metric that contains the timestamp of the most recent notification.
  • Notification Failure Message: An attribute that contains the error message corresponding to the most recent notification failure.

Issues fixed

These are the issues we have fixed in this release:

Issue key Release description
OBAN-206 Renamed targets are now correctly reflected in the value of the notification-url attribute for Slack and ServiceNow.
OBAN-209 The Snackbar error is not displayed when the error is handled from the UI with a dialog, such as when a target or notification is out-of-sync or not found.
OBAN-211 When a notification is updated with one or more targets that have been deleted, a new dialog is displayed, indicating that the targets (which are not found) will be removed from the selection.
OBAN-212 Updating the target’s channel ID now correctly updates the notification-url attribute value to point to the new channel.
OBAN-213 Previously, it was possible to save an out-of-date notification when you double-click the Save button. A dialog is now displayed indicating that the notification will be updated.
OBAN-224 Entities with their notification-url attribute removed due to a notification or target being disabled are now correctly re-tagged when the notification or target is re-enabled.

Known issues

These are the known issues affecting this release:

Issue key Known issue description
OBAN-142 The following reported security vulnerabilities have been flagged by Black Duck:
  • BDSA-2023-1680: In Keycloak, a cross-site scripting vulnerability when validating URI-schemes could allow an attacker to run a malicious JavaScript code on a compromised user’s browser, potentially exposing session tokens or other sensitive information.
  • BDSA-2023-1687: Improper validation for client certificates in Keycloak could allow an attacker with a proper certificate to authorize itself as any other client and gain access to other clients’ sensitive information.
  • CVE-2023-3635: GzipSource does not handle an exception that might be raised when parsing a malformed gzip buffer, which could lead to a denial-of-service of the Okio client.

Obcerv Notifications 2.0.0

Released: 28 June 2023

Caution

Upgrading to the Notifications app version 2.0.0 will not be compatible with previous versions of the app. Any existing notification configurations and internal states on notifications by a previous version of the app will be permanently and irreversibly deleted when you upgrade.

Caution

Before upgrading, you must first uninstall all Obcerv apps. Due to Web Platform security changes, you need to upgrade all Obcerv apps at the same time. Make sure that you reinstall the latest mutually compatible versions of Obcerv apps. See the Obcerv Compatibility Matrix.

New features and enhancements

These are the new features and enhancements of this release:

Issue key Release description
OBAN-125 Inactive entities are now detected through the inactive-since attribute instead of last-observed.
OBAN-149 Renamed Conditions field to Filter in the main configuration screen.
OBAN-150 Improved error handling when configuring the notification trigger timings.
OBAN-151 Decoupled integration-specific target configurations from the main configuration screen and moved them to a new screen. You can now manage targets independently of notifications, while multiple notifications can now use the same target. Notifications may only use targets of the same type, such as Slack. The Notification app has also been moved out of Alerting and into its own top-level item on the sidebar.
OBAN-183 Restricted notification and target names to a maximum of 50 characters, and notification and target descriptions to a maximum of 150 characters.
OBAN-188 Cloned notification configurations are now disabled.
OBAN-191 User actions related to CRUD operations on target and notification configurations are now logged in a parsable and searchable format.
OBAN-194 A placeholder message is now shown when no targets have been configured for an integration.
OBAN-195 Improved error messages when saving a notification or target configuration.
OBAN-196 Notification configurations prior to version 2.0.0 of the app are removed during the upgrade.
OBAN-201 The notification entity filter and groupings cannot be modified after being set. To change the filter or grouping, the notification configuration needs to be cloned.
OBAN-204 Notification and target names are now limited to 50 characters, while notification and target descriptions are limited to 150 characters.

Issues fixed

These are the issues we have fixed in this release:

Issue key Release description
OBAN-134 Attempting to enable a draft notification prior to setting the mandatory notification target fields no longer results in an error.
OBAN-137 The notifications table has been made adaptive to the screen size.
OBAN-138 Entities are now correctly tagged with a Slack permalink when a Slack channel name is used in the configuration instead of an ID.
OBAN-148 The ${url} placeholder now points to the correct Obcerv URL.
OBAN-175 Notifications are no longer triggered on inactive entities.
OBAN-176 A more meaningful error message is shown when trying to save a grouped notification using a placeholder that is only available for non-grouped notifications.

Known issues

These are the known issues affecting this release:

Issue key Known issue description
OBAN-125 Entities tagged by the app with the notification-url attribute that become inactive are automatically untagged to indicate that they are no longer tracked. This unintendedly reactivates the entity and prevents it from being eligible for eviction.
["Obcerv"] ["Release Notes"]

Was this topic helpful?