Data Observability platform Help

Alerts settings

Alerts

The Alerts tab combines three sections in one view:

  • SMTP settings - outbound email server configuration

  • User alerts management - centralized view of every alert subscription across all users (see Managing user alerts)

  • Webhooks - outbound webhook destinations

SMTP settings:

  • SMTP host – host of your email server

  • SMTP port – port of your email server

  • Security – encryption mode for the connection: None (no encryption), STARTTLS (port 587, upgrade to TLS), or SSL/TLS (port 465, implicit SSL)

  • SMTP user – (optional) SMTP authentication username. If left empty, the from email is used. Required for services like AWS SES where the SMTP username differs from the sender address

  • Password – password for email if authentication is needed

  • From email – email that will send out reports

  • Subject – email subject title

Webhooks:

  • Name - Webhook name

  • Url - Webhook URL

Adding webhooks

CustomWebhook
  • Name – Webhook identifier name

  • Url – Webhook URL

  • Body – JSON body for the webhook, which will be executed with POST request.

The webhook editor shows the full list of placeholders in a left-hand panel - click any placeholder to copy it to clipboard for pasting into the body.

Parameters:

  • ${name} - Test suite/object name

  • ${connection} - Connection name

  • ${passed} - Passed percentage

  • ${failed} - Failed percentage

  • ${error} - Error percentage

  • ${url} - Link to the failed test suite/object in the application

  • ${report_url} - Authenticated download URL for the test suite report (Excel/HTML attachment). Distinct from ${url}, which deep-links into the UI.

  • ${test_cases} - List of all test cases with results, ordered by status (failed first, max 10 test cases). Each test case includes:

    • ${description} - Test case description

    • ${status} - Execution status

    • ${expected_result} - Expected result value

    • ${result} - Actual result value

    • ${execution_time} - Execution duration

    • ${previous_result} - Previous execution result

    • ${labels} - Test case labels

  • ${/test_cases} - Close test cases tag

Sample templates

The webhook editor ships with four ready-made body templates - click a template chip above the JSON editor to load it, then customize as needed:

  • Simple text - flat text payload with a text field; works with any service that renders Markdown in chat messages.

  • Slack blocks - Slack Block Kit payload with summary text and two action buttons (View results, Download report).

  • Teams - Microsoft Teams Adaptive Card payload with a fact set and open-URL actions.

  • Generic - flat JSON object with one key per placeholder. Useful as a starting point for arbitrary REST endpoints (Jira issue creation, PagerDuty, internal services, etc.) where you can map the fields to whatever the target API expects.

Editing webhooks

  1. Click on webhook you want to edit

  2. Refer to Adding webhooks.

Managing user alerts

Admins can review and manage every alert subscription in the system from a single table in the Alerts tab

manageUserAlerts.png

The table lists one row per subscription, with these columns:

  • User - display name and email of the subscriber

  • Object type - Test case, Test suite, Term, Object, or Profiling

  • Object name - the entity the user is subscribed to

  • Scopes - which kinds of events trigger an alert for this subscription (see below)

  • Created at - when the subscription was created

The table supports text search by user, text search by object name, and multi-select filters on object type and scopes.

Alert scopes

Each subscription has one or more scopes that decide when it fires. Which scopes are available depends on the object type:

Object type

Available scopes

Test case

Audit alert, Failure alert

Test suite

Failure alert

Term

Audit alert

Object

Audit alert

Profiling

Failure alert

  • Failure alert - fires when an execution of the entity reports a failure (or below the configured threshold)

  • Audit alert - fires when the entity's configuration is changed (edits, renames, deletes)

Editing a subscription

Click any row to open the edit modal. Toggle the scopes you want and Save. Removing every scope unsubscribes the user from that entity (a confirmation is shown). Admins can also select multiple rows with the row checkboxes and bulk-remove subscriptions from the toolbar.

My alerts (non-admin view)

Non-admin users see a My alerts tab in their profile settings with the same table, filtered to their own subscriptions. The columns are the same, minus the User column, and they can edit or remove only their own subscriptions.

21 May 2026