Bulk Monitoring Policy

Bulk Monitoring Policy lets you define alert rules that apply across multiple pipelines at one time. Unlike monitoring policies configured from an individual pipeline detail page, bulk monitoring policies are created from the Pipelines page and can target one or many pipelines through a single policy.

With Bulk Monitoring Policy, you can apply a uniform threshold condition across all selected pipelines, or configure distinct thresholds and severity levels per pipeline. You can also choose how alerts are delivered: as immediate per-breach notifications, as a scheduled summary across all pipelines in the policy, or both.

At this time, Bulk Monitoring Policy supports only the Pipeline Duration metric.

Access the Monitoring Policy Page

To open the Bulk Monitoring Policy view:

1. In the left sidebar, navigate to Discover -> Pipelines.
2. On the Pipelines page, click the Monitoring Policy tab.

This tab lists all bulk monitoring policies currently defined in your namespace. Each entry shows the policy name, description, the number of pipelines attached to the policy, and the date the policy was created or last updated. From here, you can create, edit, or delete policies.

Create a Monitoring Policy

To create a monitoring policy, click Add Monitoring Policy. The policy creation form opens and guides you through the following steps.

Step 1: Select Pipelines

Choose the pipelines this policy will monitor. You can select a single pipeline or multiple pipelines. Use the + Add Pipeline option to add pipelines to the selection.

Step 2: Configure Metric and Threshold

Define the condition that triggers an alert. Bulk Monitoring Policy currently supports only the Pipeline Duration metric.

Use the Global Condition and Individual Condition toggle to choose how thresholds are applied:

• Global Condition: Applies a single threshold condition and severity level uniformly to all selected pipelines. Use this when all pipelines in the policy share the same SLA or performance expectation.
• Individual Condition: Allows you to configure a distinct threshold, operator, value, and severity level for each pipeline in the policy. Use this when pipelines have different expected durations or different alert priorities.

Note __Switching between Global Condition and Individual Condition during policy creation resets any threshold values already entered.

Step 3: Configure Notification Mode

Choose how alerts are delivered when a policy condition is breached. Three notification modes are available:

• Instant Alerts: Sends a notification immediately each time an individual policy execution breaches the configured threshold. This is the same behavior as in previous releases. Select the notification channel for instant alerts using the Where should we send instant alerts? field.
• Scheduled Summary: Sends a single aggregated notification at a configured interval — for example, hourly, every six hours, or daily. The summary reports the status of all pipelines in the policy for the configured window. A pipeline is marked as failed if any policy execution within the window breached its threshold; it is marked as passing if all executions within the window passed. Configure the interval and notification channel separately for the summary.
• Instant + Summary: Enables both modes simultaneously. You can configure separate notification channels for instant alerts and the scheduled summary.

Step 4: Name and Describe the Policy

Enter a Policy Name (required) and an optional Description to identify the policy in the listing view.

Step 5: Review and Activate

Review the policy configuration, including the selected pipelines, threshold conditions, notification mode, and notification channels.

When you save the policy, it is created in a Draft state. The policy does not begin monitoring pipelines until it is explicitly activated. To activate the policy, locate it in the Monitoring Policy listing and change its status to Active.

How the Policy Triggers Alerts

After a pipeline run completes, ADOC evaluates the run against all applicable bulk monitoring policies. If a run breaches a configured threshold, ADOC generates an alert and sends a notification through the selected channel.

For Instant Alerts, a notification is sent for each individual policy execution that breaches the threshold.

For Scheduled Summary notifications, ADOC evaluates all pipeline executions within the configured summary window and delivers a single aggregated notification. The summary classifies each pipeline in the policy as follows:

• Failed: One or more policy executions within the summary window breached the configured threshold.
• Passed: All policy executions within the summary window met the configured threshold.

Alerts generated by bulk monitoring policies are also visible in the ADOC UI in the Alerts section and on the Pipelines page.

What's Next

After completing this section, explore:

• Pipeline Run Details – Investigate a specific run that triggered an alert.
• Manage Pipelines – Configure monitoring policies and automated data reliability checks for an individual pipeline.
• Pipeline Observability – Understand how ADOC models pipelines, runs, spans, and events end to end.