Alert routing

Metaplane provides a flexible means of routing alerts based on rules such as the type of alert as well as the alert's content. For example, you can send alerts for a specific database, schema, table, column or custom monitor to the teams that own those various assets.

In the example above, the #analytics-alerts channel is configured to only get alerted of schema changes and incidents related to analytics assets while #data-awareness is notified of broader alerts.

Configuring alert rules

Once you've added an alert destination, you can then configure rules that describe how you'd like for Metaplane alerts to get routed.

There are 2 types of alerts:

  1. Incident alerts
  2. Schema change alerts

Incident alerts

Incident alerts are sent when Metaplane has detected data quality issues.

To configure rules for this type of alert click the "+ Add incident rule" button.

You can then configure the rule, e.g., send alerts to this destination for an entire schema or dbt project.

Schema change alerts

Schema change alerts are sent when Metaplane has detected a schema change.

To configure rules for this type of alert click the "+ Add schema change rule" button.

In the example above, changes related to schemas that start with "tmp_" will be filtered out of the schema change alert.

The rule configuration screen will allow you to apply the rules such as:

  1. Whitelisting schemas/tables/columns based on exact name matches, prefixes, suffixes, or regexes
  2. Ignoring schemas/tables/columns based on exact name matches, prefixes, suffixes, or regexes

These rules can be applied both across the entire database and for specific schemas by pressing Add a schema-specific rule.

Multiple entries for the same rule should be listed in the text box using comma separation. For example, to ignore schemas starting with either test or dev, you would list test, dev in the rule text box. Note that test,dev is different from test, dev due to the space after the comma — the former would ignore schemas that start with the literal string "test,dev" which, in this case, is not what we'd want.

Creating a rule set using the default, unmodified, rules will perform no filtering on the schema change rules. You can always go back and edit these rules later.

Schema changes can also be viewed from the the Schema changes page.