Skip to content

Alerts

Automation sends alerts by email for various states of every order run. You can configure notification recipients at both the kitchen and recipe levels.

Events that generate alerts

  • Start: an order run started.
  • Warning: an order run met the threshold set for the number of node test warnings.
  • Time Limit Exceeded: an order run met the threshold set for the maximum process time for an order.
  • Success/Complete: an order run completed successfully.
  • Failure/Error: an order run failed.

Visual example

()

Alert Details

While the email alerts are a point-in-time status report, the Order Run Details page is the best resource for verifying or troubleshooting order runs.

View the current order run

  • From an email alert, click the linked Order Run ID to access the Order Run Details page for that order.
  • From the Orders page, click the linked Order Run ID.
  • From the command line, issue the orderrun-info command. See CLI Order Run Details for more information.

View order runs over time

  • From an email alert, click the linked Order ID to access the Variation Metrics page with test and timings data for all order runs in the recipe variation.
  • From the Orders page, click the linked Recipe/Variation to access the Variation Metrics page.

Alert integrations

In addition to email notifications, you can configure alerts to display in Slack o ;Microsoft Teams.

  • Slack: Use the email integration. This app generates a custom email address, which you can then enter in your DataKitchen alert configurations. Any emails sent to that address are displayed in the specified Slack channel.
  • MS Teams: See Office Support and the MailClark app for options on how to integrate email in Microsft Teams.

Tip

Consider segmenting the alerts you send to Slack or Teams by alert type (alert or error) and by release environment (dev or prod), so that DataKitchen alerts appear in different channels.

Alerts configuration

Configure alerts at the kitchen level, at the recipe level, or both. During setup, specify alert recipients and select the event types that send notifications.

For some alert types, a threshold at the variation level must be set.

As a best practice, users should set alerts for their kitchens because recipe alert settings get promoted during merges to parent kitchens. Recipe alerts should be used for temporary testing only.

Note

When both kitchen and recipe alerts are configured, the system sends emails to both recipient lists but does not send duplicate emails. The two configurations are ANDed; one does not override the other.