Alerts
This document explains the Alerts page in Acceldata Data Observability Cloud (ADOC). The Alerts page allows you to select a global time filter from Global Calendar. Only those alerts that occurred during the selected time filter are displayed. The alerts are displayed for compute monitors, pipeline monitors, and policy monitors.
To navigate to the Alerts Overview page, execute the following steps.
- Log in to your ADOC account.
- Navigate and click on Alerts in the left pane.
Alerts: This table displays a list of monitors for which alerts have been raised. The monitor list depends on the filter applied in the global calendar.
| Column Name | Description |
|---|---|
| Name | Name of the alert. |
| Severity | The severity of the alert. Possible values are Critical, High, Medium, and Low. |
| Type | The observability for which the alert was raised. Possible values are Compute, Pipeline, and Reliability. |
| Status | The status of the alert after it was raised. Possible values are Open, Acknowledge, In Progress, Dismiss, and Resolved. If multiple incidents are raised for an alert, the status of the latest incident raised, is displayed. |
| Raised | The date and time when the alert was raised. |
| Updated by | The name of the individual or role who modified the alert is displayed. |
| Assignee | Displays the name of the user to whom the alert has been assigned. |
| Occurrence Count | The number of times the alert was raised in the last 30 days. |
| Last Updated At | The date and time when the alert was last raised. |
If an alert is raised multiple times for a monitor, you can view only one instance of the alert. The Count column displays the number of times the alert was raised. The Last Raised at column displays the last date and time when the alert was raised. If the Group by option is enabled in the parent monitor, you can view multiple instances of the alert, based on the group by option configured.
In ADOC, users have the ability to configure alert generation for data reliability policies. While alerts remain mandatory for policy failures, there is now an option to customize how these alerts are generated.
- Updates to Existing Alerts: If the same policy fails multiple times, the existing alert will be updated rather than creating new alerts each time. This approach helps keep alert management more organized and less cluttered.
- Notification Frequency: Notifications for policy failures are sent only for the first failure. This change is significant as it reduces the number of notifications received by users, addressing the issue of notification overload. Users will not receive repeated notifications for subsequent failures of the same policy.
Alert Bulk Actions
ADOC allows you to perform bulk action on the alerts list page. You can select multiple alerts or select the global check box at the top of the page to enable alert bulk actions.
There are three types of bulk actions supported. Alert status, alert severity, and alert assignee. You can modify the status or severity of multiple alerts by using the bulk actions feature. The status, severity, or assignee of all the selected alerts is modified.
Alerts have five status. It is necessary to understand how each status works. This section explains the working of each of the five status. While setting this status, users must provide information as to why they are setting a specific status, in the comments section.
- Open: An Open status is the default status of the alert when it is raised. Any user who looks into the alert must change the status from open to any other suitable status.
- Acknowledge: An acknowledge status must be marked by a user when they have viewed the alert and are due to take the necessary actions shortly.
- In Progress: Users must set alert status to In progress when they have started to work towards the resolution of the alert.
- Dismiss: The dismiss status is set in two scenarios. In the first scenario, ADOC automatically sets the alert to dismiss status, if the parent monitor is updated, after the alert is generated. A user can also set the status to dismiss, if they feel that the alert is not serious enough to take an action. While setting this status, users must provide information as to why they are setting the status as dismiss, in the comments section.
- Resolved: The resolved status is set in two scenarios. If an alert is raised and if the parent monitor's Query conditions are modified such that they do not meet alert conditions and if Auto resolve option is enabled in the monitor, ADOC resolved the alert automatically. Users can set the status to resolved, if they have resolved the issue.
Alert Filters
To view alerts specific to an entity, you must apply filters. The filters are available in the left pane of the alerts page. ADOC provides you with the following filters:
- Datasource Name: This filter allows you to filter data sources by their names.
- Type: This filter allows you to filter alerts by the observability type for which they were raised; Compute, Pipeline, and Reliability.
- Status: This filter allows you to filter alerts by the status of the alerts. Possible values are Open, Acknowledge, In Progress, Dismiss, and Resolved.
- Severity: This filter allows you to filter alerts by the severity of the alerts. Possible values are Critical, High, Medium, and Low.
- Assignee: This filter allows you to assign the alerts to a user who can reply to the notifications.
- Tags: For Databricks compute resources, tags associated with a Databricks cluster are automatically applied to alerts generated for that cluster, provided the monitor is configured specifically for a Databricks cluster. This filter allows you to filter and view alerts tagged with specific keywords. Additionally, the Tags column has been added to the alert listings on the Alerts List panel, offering a quick overview of each alert's associated tags.
Alert Detail View
The alert detail view displays all the details of the alert. Some details are applicable only to a specific data source (Snowflake, Databricks) and some details are applicable only to Stock alerts.
Accessing the Alert Details Page
To reach the Alert Details page:
- From any ADOC page, click on the Alerts icon from the left-hand navigation menu.
- Select an alert from the list to view its detailed information.
Overview Tab
The Overview tab consists of several sections and visual elements.
The various sections of the overview tab are as follows:
Alert Information Header: Displays the name of the alert and critical information such as severity level, expected vs. actual score, and threshold status.
Severity Indicator: A colored icon indicating the severity level (e.g., critical, warning) of the alert.
Scorecard: Shows the Expected Score versus the Actual Score, and the Threshold level which triggers the alert.
Policy and Asset Information:
- Raised On : Date and time when the alert was triggered.
- Policy Name : Name of the policy associated with the alert.
- Assets : Shows the data asset path, typically from a data source (e.g., Snowflake) to the specific data asset (e.g., table) affected by the alert.
Impacted Assets Section: This section provides details on assets impacted by the alert:
- No Impacted Assets Message : If there are no assets affected by the alert, a message stating
No impacted assets for this alertis displayed. If there are impacted assets, they will be listed with relevant information for further action.
- No Impacted Assets Message : If there are no assets affected by the alert, a message stating
Execution Summary Chart: The Execution Summary provides a visual representation of the alert over time:
- Metric Type Dropdown : Allows you to select different types of metrics (e.g., Data Freshness) to view on the chart. Timeline Chart: Shows the SLA breach instances over a timeline with the duration of the breach highlighted.
- SLA Breach Indicators : Markers on the chart indicate specific points where an SLA breach occurred, with the actual duration and status labeled (e.g., "SLA Breached").
Lineage Tab
The Lineage tab on the Alert Details page in ADOC provides a visual representation of the data lineage associated with a specific alert. This guide will assist users in interpreting and navigating the Lineage tab for efficient data management.
The diagram illustrates how different data entities are connected through various processes:
- Suppliers and Consumers : Entities that supply data to or consume data from the affected node are displayed, providing insight into upstream and downstream dependencies.
- Path Highlighting : Connections between nodes are highlighted to show the path of data flow.
Components of the Lineage Tab
| Components | Descriptions |
|---|---|
| Data Nodes | Represent data entities such as tables, files, or databases. In the example, CADENCE_TABLE is highlighted as an affected node. |
| Process Nodes | Represent operations or transformations applied to the data, like Query Insert. |
| Node Status Indicator | Nodes may have status indicators, such as an alert icon on CADENCE_TABLE, denoting an issue that needs attention. |
You can interact with the diagram in several ways:
- Toggle Views: Use the checkboxes to show or hide sub-level lineage, impact analysis, and only impacted nodes for a simplified or detailed view.
- Zoom and Pan : Utilize mouse actions or touch gestures to zoom in/out and move around the lineage diagram for better visibility.
- Node Exploration: Click on individual nodes to view more details or to investigate related alerts.
- Reset and Refresh: The Reset button located at the top right corner of the lineage diagram allows you to return to the default view after zooming or panning. Users can refresh the data on the page to see the most current lineage information.
The Lineage tab on the Alert Details page is a powerful tool within ADOC for tracing the origin, transformation, and destination of data related to an alert. By leveraging the visual lineage diagram, you can gain insights into the data lifecycle, understand the context of alerts, and take informed actions to maintain data integrity and reliability.
History Tab
The History tab on the Alert Details page of ADOC offers a chronological record of past incidents related to a particular alert.
The History tab contains the following elements:
| Components | Descriptions |
|---|---|
| Raised at | The date and time when each incident was raised. |
| Policy Score | The score assigned to the alert based on the defined policy. |
| Occurrence | The number of times the incident occurred. |
| Closing Reason | The reason provided for the closing of the alert, if applicable. |
| Action | An option to view more details about the specific alert incident. |
| 10 Past Incidents | The page displays the 10 most recent past incidents by default. |
The History tab is an essential feature within ADOC that provides users with insight into the alert's performance over time. By reviewing the historical data, teams can better understand the context of alerts, address recurring issues, and make informed decisions to improve data reliability. This historical perspective is crucial for continuous improvement in data observability and operational excellence.
User Feedback
To improve the alert system, users have the option to submit feedback directly on the Alert Details page. By clicking the
Snooze Alerts
ADOC provides the ability to temporarily disable notifications by snoozing them for a specific time period. To snooze an alert notification, go to the Alerts Detail page, locate the
To resume receiving notifications for a snoozed alert, click on the
If you cannot see the bell icon, make sure you have the Viewer role permission enabled. On the Alerts page, users with the appropriate permissions can view and snooze notifications by selecting a date range.
Assignee
Assignee is a new feature which is added in the ADOC version 2.7.0.
A Administrator can assign one alert or many alerts to another user by selecting the Assignee button on the Alerts page. This functionality is useful for teams where many users are assigned distinct alert actions. It encourages better teamwork and accountability.
After the alert is assigned, an email alert is sent to the assigned user (the assignee). The assignee can view the Alerts page by clicking the View Alert button. This lowers the possibility of the assignee finding whether or not an alert has been issued to them and who has assigned it to them.
The assignee is now aware of their tasks and can take the appropriate activities in a timely way, resulting in enhanced task management and overall productivity.
Assignee Email Notifications
When numerous alerts are assigned to a single assignee, the assignee receives the following email notification. Clicking on View Alerts takes the assignee to the view page, where they can click on specific notifications.
Assignee Bulk Email Notifications