PagerDuty Notification
Integrating PagerDuty with Qualytics ensures that your team gets instant alerts for critical data events and system issues. With this connection, you can automatically receive real-time notifications about anomalies, operation completions, SLA violations, and other important events directly in your PagerDuty account. By categorizing alerts based on severity, it ensures the right people are notified at the right time, speeding up decision-making and resolving incidents efficiently. This helps your team respond quickly to issues, reducing downtime and keeping data operations on track.
Navigation to Notifications
Step 1: Log in to your Qualytics account and click the Settings button on the left side panel of the interface.
Step 2: By default, you will be navigated to the “Tags” section. Click on the Notifications tab.
Add PagerDuty Notification
Step 1: Click on the Add Notifications button located in the top right corner.
A modal window Add Notification Rule will appear providing you with fields to set notification rules.
Step 2: Enter the following details to add the notification rule.
1. Name: Enter a specific and descriptive title to your notification rule to easily identify its purpose.
2. Description: Provide a brief description of what the notification rule does or when it should trigger.
3. Trigger When: Select the event or condition from the dropdown menu that will trigger the notification. Below is the list of available events you can choose from:
-
Operation Completion: This type of notification is triggered whenever an operation, such as a catalog, profile, or scan, is completed on a source datastore. Upon completion, teams are notified through in-app alerts, and notifications are also sent directly to PagerDuty. For example, when a catalog operation is completed, a notification is automatically sent to PagerDuty, allowing for immediate action.
-
An Anomaly is Identified: This type of notification is triggered when any single anomaly is identified in the data. The notification message typically includes the type of anomaly detected and the datastore where it was found. It provides specific information about the anomaly type, which helps quickly understand the issue's nature.
Tip
Users can specify a minimum anomaly weight for this trigger condition. This threshold ensures that only anomalies with a weight equal to or greater than the specified value will trigger a notification. If no value is set, all detected anomalies, regardless of their weight, will generate notifications. This feature helps prioritize alerts based on the importance of the anomalies, allowing users to focus on more critical issues.
- Anomalies are Detected in a Table or File: This notification is triggered when multiple anomalies are detected within a specific table or file. It includes information about the number of anomalies found and the specific scan target within the datastore. This is useful for assessing the overall health of a particular datastore. No concept of weights.
| Factors | An Anomaly is Identified | Anomalies are Detected in a Table or File |
|---|---|---|
| Trigger Event | Notifies for individual anomaly detection | Notifies for multiple anomalies within a specific table or file |
| Notification Content | Focuses on the type of anomaly and the affected datastore. | Provide a count of anomalies and specifies the scan target within the datastore. |
| Notification Targeting | Tags, Weight or both | Only Tags |
- A Freshness SLA Violation Occurs: This type of notification is triggered when data within a datastore does not meet the defined freshness criteria, violating the Service Level Agreement (SLA). The notification message typically includes details about the extent of the violation, the specific datastore affected, and the freshness threshold that was breached. This helps the team take prompt corrective actions to ensure data timeliness and reliability.
4. Message: Enter your custom message using variables in the Message field, where you can specify the content of the notification that will be sent out.
Tip
You can write your custom notification message by utilizing the autocomplete feature. This feature allows you to easily insert internal variables such as {{ rule_name }}, {{ container_name }}, and {{ datastore_name }}. As you start typing, the autocomplete will suggest and recommend relevant variables in the dropdown.
5. Datastore Tags: Use the drop-down menu to select the datastore tags. Notifications will be generated for only those source datastores that have the datastore tags you select in this step. For example, if you select the “critical” datastore tag from the dropdown menu, notifications will be generated only for source datastores having the "critical" tag applied to them.
Note
If you choose "An Anomaly is Detected" as the trigger condition, you'll need to define the Anomaly's Tag and set a minimum Anomaly weight. This means that only anomalies with a weight equal to or greater than the specified value will trigger a notification. If no value is set, the weight will be ignored.
6. Notification Channel: Select PagerDuty as your notification channel and enter the Integration Key where you want the notification to be sent.
Info
For detailed instructions on creating or configuring the PagerDuty integration, please refer to the PagerDuty documentation available here.
7. Severity: Select the appropriate PagerDuty severity level to categorize incidents based on their urgency and impact. The available severity levels are:
-
Info: For informational messages that don't require immediate action but provide helpful context.
-
Warning: For potential issues that may need attention but aren't immediately critical.
-
Error: For significant problems that require prompt resolution to prevent disruption.
-
Critical: For urgent issues that demand immediate attention due to their severe impact on system operations.
Test PagerDuty Notification
Click on the Test notification button to check if the integration key is functioning correctly. Once the test notification is sent, you will see a success message, "Notification successfully sent."
This confirms that the integration is properly configured and that the PagerDuty account will receive notifications as expected.
Save PagerDuty Notification
Step 1: Once you have entered all the values and selected PagerDuty as notification channels, then click on the Save button.
After clicking the Save button, a success flash message will be displayed saying "Notification Successfully Created".
Post Results
Once you’ve saved the PagerDuty notification rule, all real-time notifications will be sent to the integration key you specified,
For example, when an operation is completed or an anomaly is detected in a table or file, a notification will be sent to the integration key you provided. This keeps you informed of critical events in real-time, allowing you to take quick action to maintain smooth operations.
