Skip to main content

​
System & Governance Notifications

Stay informed about metadata changes, governance events, and collaboration activities across your data catalog.
Tip: Use System & Governance Notifications for platform-wide metadata events — governance actions, service changes, collaboration activity, and any entity type not covered by Observability Alerts. For data health monitoring such as test failures and schema changes, use Data Observability Alerts instead.

​
Create a new Alert

  1. Navigate to Settings > Notifications > Alerts.
  2. Click Add Notification. Add Notification Button
  3. Enter a unique alert Name and Description (optional) for quick identification. Input fields for Alert Name and Description
  4. Select one or more sources to trigger this alert. Select the Source Resource for System Notifications Available source entities The sources you pick determine which entity types’ events trigger the alert. Select All to receive notifications for every entity type without filtering by source. To target a specific entity type, choose from data assets, service connections, governance entities, or collaboration threads. To watch several entity types with one alert, select each source from the list. The list groups the sources under All Events, Data Assets, and Data Collaboration. Data Collaboration holds Task, Conversation, and Announcement. Data Assets holds every other source except All, including services and governance entities. One alert can combine sources from one group only, and All can’t be combined with other sources. A source you can’t add is greyed out, with the reason under its name. Source field with Table selected, and Conversation greyed out under Data Collaboration with the reason it can't be added Data assets Service connections Governance Collaboration These three sources all relate to threads posted on data assets, but each covers a distinct thread type. Choosing the wrong one is a common source of misconfigured alerts.
    Important: Incident alerts require Task as the source, not Conversation.Incidents in Collate are Task threads, not Conversation threads. If you set Source = Conversation, the alert will never fire for incident comments, assignments, or status changes. Set Source = Task to receive notifications for incident activity.
    The Task source covers the following task types: The only filter available for Task and Conversation is Mentioned User or Team: narrow the alert to threads where a specific person or team is @-mentioned. You can’t filter tasks by task type (for example, incidents only) in the alert UI.
    Note: An alert scoped to one asset (for example, a single table) now only notifies about conversations and replies on that asset, not on every table or glossary term. If an alert on conversations seems too quiet, its scope may be narrower than you expect. Widen it if needed.
  5. Add filters to narrow the alert scope and trigger notifications for specific events.
    Note: If you don’t set any filter, the alert applies to all events over the selected source entity type.
    Use filters to narrow the alert to relevant changes. The available criteria depend on the sources selected. With several sources, only the filters that every chosen source supports are available. Filter events by:
    • Owner: Filter events based on the designated owner of the asset.
    • Entity FQN: Filter by the Fully Qualified Name of the entity.
    • Event Type: Filter by the specific action that occurred. For more details about the various event types, see the table below.
    • Updater Name: Filter based on the user or service that executed the change.
    • Domain: Filter events based on the Data Domain the entity belongs to.
    • Filter By Updater Is Bot: Filter to include or exclude changes made by automated ingestion or system processes.
    Use the Include toggle to define the logic for the filter condition:
    • Include (Toggle ON): If the event meets the filter condition, the alert is sent.
    • Exclude (Toggle OFF): If the event meets the filter condition, the alert is silenced (not sent).
    Add multiple filters to a single alert subscription. Define Filters Define Filters
  6. Add destinations where you want to deliver alerts. Select Add Destination to add one or more notification targets. Internal:
    • Admins - Notify all platform administrators
    • Assignees - Notify users assigned to the asset
    • Followers - Notify users following the asset
    • Mentions - Notify users mentioned on the asset
    • Owners - Notify the owners of the asset
    • Teams - Notify a specific team
    • Users - Notify specific individual users
    External — select a Type:
    • Email
    • G Chat
    • Ms Teams
    • Slack
    • Webhook
    (Optional) Enable Notify Downstream to also notify the stakeholders of assets downstream of the monitored entity. Notify Downstream works with the internal destinations only. For depth, recipients, and examples, see Notify Downstream. Internal Destinations External Destinations
  7. Select a Notification Template to control the wording of the message this alert sends — its subject line and body. Choose from:
    • System Default Template — the built-in wording, used when nothing else is selected.
    • A saved template — a reusable template created in Notification Templates.
    • Create Custom Template — wording written here and belonging to this alert alone.
    For full details on creating and managing templates, including Handlebars placeholders, helpers, and examples, see Notification Templates.