DataKitchen DataOps Documention

The DataKitchen platform sends alerts via email for various states of every order run. Users can configure the recipients of these notifications at both the kitchen and recipe levels.


The platform sends email notifications when an order run moves into any of the following states.

Event Types that Generate Alerts

  • Start: An order run started
  • Success/Complete: An order run completed successfully
  • Failure/Error: An order run failed
Sample alert emailed to a user

Sample alert emailed to a user

Alert Integrations

In addition to email notifications, users can configure alerts to display in Slack channels or Microsoft Teams channels.

  • Slack: An app add-on supports email integration. The app generates custom email address, which you can enter in your DataKitchen alerts configurations. Any emails sent to that address are displayed in your specified Slack channel.
  • MS Teams: There are a number of ways to integrate email in your Teams channels. See Office Support and the MailClark app for options.

Alerts Tip

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

Viewing Order Run Details

The Order Run Details page contains all information related to the run. While the alert emails are point-in-time status reports, this page is the best resource for verifying or troubleshooting order runs.

View the current order run

  • From an alert email, click the linked Order Run ID to access the Order Run Details page for that order. See UI Order Run Detail for more information.
  • 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 alert email, click the linked Order ID to access the metrics for all order runs in the recipe variation in the kitchen.
  • From the Orders page, click the linked Recipe, Variation.

Alerts Configuration

Users can configure alerts at the kitchen level or at the recipe level or both.

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.

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.

Configure Kitchen Alerts

The Alerts tab on the Configure Kitchen page offers a simple interface to set alert recipients and the type of alerts they will receive. The system will send alerts for any orders run in the kitchen to the listed recipients for the specified event types.

  1. Click the wrench icon associated with the kitchen to open the Configure Kitchen page.
  2. Click the Alerts tab.
  3. Click the Add Recipient button.
  4. In the Email field, enter an email address for the new recipient, or select an address from the drop-down list of active users.
  5. Check one or more checkboxes to enable order run alerts by event type for the recipient.
  6. Add more recipients as needed.
  7. Click the Update button.

Configure Recipe Alerts

Users can configure alerts at the recipe level, which are useful for temporary, localized testing.

Following best practices, users should set recipe variables for email recipients, then reference those variables in the recipe description fields.

Recipe Alerts Merge Up!

Any recipe-level alerts you set will be promoted to a parent kitchen during a kitchen merge. Ensure that the alert settings are appropriate or remove them before merging.

Creating alerts variables
You can set alerts variables in the Variables tab on the Variation page or in the variables.json file for the recipe.

  1. On the Variation page, click the Variables tab.
  2. Click the Add Variable button and enter a name, such as "alerts."
  3. Click in the Recipe Value field, and enter a JSON string to list email recipients for each of the four event types.
  4. Click the Update button.

The following examples show how you can set recipients in the web app tab or in the JSON file.

Users can set alert variables on the Variations page.

Users can set alert variables on the Variations page.

    "variable-list": {
        "alerts": {
            "start": [
                "[email protected]",
                "[email protected]"
            "success": [
                "[email protected]",
                "[email protected]"
            "failure": [
                "[email protected]",
                "[email protected]",
                "[email protected]"

Referencing variables during alerts setup
The Recipes page provides access to an Alerts dialog as an interface for the underlying description.json file.

  1. On the Recipes page, select a recipe from the list on the left.
  2. Using the Recipe Actions drop-down list at the top right of the page, select Edit Alerts.
  3. In the Edit Recipe Order Run Alerts dialog, click the Add Recipient button.
  4. In the Email field, select a pre-set variable or enter an email address for a new recipient.
    To follow best practices, enter addresses directly into description.json only on a temporary basis for testing. Define the recipients as variables in the recipe's variables.json file for longer-term testing.
  5. Check one or more checkboxes to enable order run alerts by event type for the recipient.
  6. Add more recipients as needed.
  7. Enter a description of your changes in the Custom change message field, and click the Update button.

Alternatively, you can switch to the File Editor and edit the recipe's description.json file manually.

    "description": "All tests to run in staging environment",
    "recipe-emails": {
        "recipe-over-duration-email-estimated-maximum-time-in-minutes": "240",
      	"email-delivery-service": "aws-email",
        "recipe-complete-email-recipients": "{{alerts.success}}",
        "recipe-error-email-recipients": [

Avoid Non-Portable Alerts

You can hard-code alert recipients in the description.json file, or you can define alert variables as kitchen overrides and reference the variables in every recipe. These methods are not optimal, however, because you have to copy the configurations across recipes or enforce a standard variable naming convention.

Updated a day ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.