Get Notifications for Alerts

Configure alert notifications to define which alerts trigger notifications and who receives them. By configuring notifications, you make sure the right people are informed about the issues that matter to them, through their preferred channels.

How notifications work

Notifications are separate from alerts. Alerts are created automatically from findings. A notification is sent to its audiences only when an alert matches its criteria, either when the alert is created or when it’s updated.

View notifications

Select Alerts from the quick access menu.
Select the Notifications tab.

The notifications list displays all configured alert notifications with the following information:

Name: The notification name.
Alert finding: The finding types this notification matches.
Alert severity: The severity levels this notification matches.
Assets: The number of specific assets this notification is scoped to.
Alerts: The number of alerts that have matched this notification configuration.
Audiences: The audiences who receive this notification.

Use the filters to find specific notification configurations by severity, finding type, or associated assets.

Create a notification

Select Create alert notification.

You can access this from several places:
- On the Notifications tab of the Alerts page.
- On the Alerts feed tab, where the button appears above the alerts list.
- On the Alerts tab of a catalog item or job detail page, to create a notification scoped to that specific asset.
Enter a Notification name.

Choose a descriptive name that reflects the purpose, such as "Critical DQ alerts for Customer data" or "All pipeline failures."
Configure the Matching criteria to define which alerts trigger this notification.

Alert severity

Select one or more severity levels: Critical, High, Medium, or Low.

Finding type

Select one or more finding types. Finding types are grouped under categories: Pipeline monitoring, DQ monitors, Profiling anomalies, Freshness, and Schema changes. For the finding types in each category, see Finding types.

Assets

Optionally scope this notification to specific assets. Select Add catalog items or Add jobs to choose specific assets.

If you create a notification from a catalog item or job detail page, that asset is automatically added to the scope. You can add additional assets or remove the pre-populated asset if needed.

With no criteria defined, the notification is triggered by all alerts. As you add criteria, an indicator shows how many alerts in the past seven days would have matched your current configuration.

In Audiences, select Add to choose one or more audiences who receive notifications.

Audiences must be created before they can be selected. See Create an Audience for instructions.
Select Save.

Edit a notification

On the Notifications tab, find the notification you want to edit.
Select the three-dot menu and choose Edit.
Update the notification configuration as needed.
Select Save.

Delete a notification

On the Notifications tab, find the notification you want to delete.
Select the three-dot menu and choose Delete.
Confirm the deletion.

Deleting a notification stops future notifications from being sent for matching alerts. It does not affect alerts or notifications that have already been sent.

Best practices for creating alert notifications

Start broad, then refine: Consider starting with a notification that captures all critical alerts, then create additional notifications for specific teams or asset groups as you learn what notifications are most valuable.
Use descriptive names: Name notifications clearly so team members understand their purpose at a glance. Include the scope (such as asset type or team) and the criteria (such as severity or finding type) in the name.
Avoid notification fatigue: Be selective about what triggers notifications. Not every alert needs to generate a notification, so use severity and finding type filters to focus on what truly requires immediate attention.
Leverage asset scoping: Create targeted notifications for high-priority assets. For example, a notification for production pipeline failures can have different audiences than a notification for development environment issues.

Notifications log

The notifications log is a record of all notifications that have been sent. Use it to confirm delivery, check which recipients were notified, and troubleshoot cases where a notification might not have arrived.

To access the log, go to Global settings > Notifications > Notifications log.

To access Global settings, select the Ataccama logo.

The log shows each sent notification with its type, message preview, destination, status, and timestamp.

Next steps

Create an Audience: Define audiences to receive notifications.
Investigate Alerts: Learn how to view and manage alerts in the feed.
Freshness Monitoring: Set up freshness monitoring and route its alerts.
Schema Change Monitoring: Choose which schema changes raise an alert.

Was this page useful?