Pipeline notifications🔗

This how-to guide explains how registered Data Productivity Cloud users can set up and monitor the status of their data pipelines using pipeline notifications.

Use cases🔗

Environment-specific routing: Send development failures to a sandbox channel and production alerts to your high-priority alerts channel.
Noise reduction: Rather than building alerts into every pipeline, simply subscribe to a project or environment once.

Prerequisites🔗

Before setting up pipeline notifications, ensure the following:

You have a registered Data Productivity Cloud account.
You have access to the relevant projects and environments where the data pipelines are running.
If you plan to use Slack notifications, you have access to a Slack workspace and a configured Slack webhook URL.

Slack setup🔗

To use Slack notifications, you must first create a Slack app and generate an incoming webhook URL in your Slack workspace. For step-by-step instructions, see Sending messages using incoming webhooks.

Overview🔗

Pipeline notifications allow you to subscribe to alerts for pipeline failures within projects and environments you have access to. These alerts help you respond quickly to issues, minimizing downtime, and improving overall reliability.

Notifications can be delivered via:

Email
Slack

Pipeline notification behavior🔗

Eligibility: Any user with access to a project or environment can subscribe to pipeline notifications.
Notification triggers: Notifications are sent when a pipeline run fails.
Scope: Notifications are sent for failures in pipelines triggered by schedules or API executed pipelines.

Note

Pipelines run manually through Designer don't generate notifications.

In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
Click the Add notification button at the top.
In the Add notification dialog, select the Project and Environment you'd like to be notified about.
Under How do you want to receive this notification, choose one or more delivery methods:
- Email
- Slack
If you select Slack:
- Enter the Slack Webhook URL generated in your Slack workspace.
- Enter a Slack Webhook Name to help you identify the webhook later.
Note
- By default, the Run failure checkbox is selected to indicate when notifications apply only to scheduled and API-triggered runs—manual runs don't trigger alerts.
Click Add.

When a notification has been added, you'll receive alerts for any pipeline failures in the selected project that run in your chosen environment. You can manage your notification settings at any time to stop receiving alerts.

The notification includes key details about the pipeline failure, such as:

Project name.
Environment name.
Pipeline name.
Time of failure.

It also provides links to the Pipeline Observability dashboard and the Notifications page for further investigation.

Managing pipeline notifications🔗

After creating a notification, you'll return to the Notifications page, where your pipeline notification has been added, displaying the following:

Project name.
Environment name.
Trigger status.
Delivery method (Email, Slack, or both).

To edit a pipeline notification, click the pencil icon next to it. Modify your previous selections as needed, then click Save to apply the changes.

To permanently remove a pipeline notification, click the bin icon next to the pencil icon. Then click Delete to confirm the deletion.

Note

If you change your mind, you can cancel the deletion action by clicking Cancel in the confirmation dialog.

Got feedback or spotted something we can improve?

We'd love to hear from you. Join the conversation in the Documentation forum!