Adobe Experience Platform provides several predefined alert rules that you can enable for your organization. This document covers the details of these Adobe-provided alert rules. For more general information on alerts in Experience Platform, see the alerts overview.
When viewing alert rules in the Platform UI, you can subscribe to each rule individually. When subscribing to alerts through I/O Event notifications, however, alert rules are organized into different subscription packages. In the tables below, each rule is shown with its corresponding I/O Event subscription name.
The following alert rules are specific to Data Ingestion and sources:
I/O Event subscription | Alert rule | Description | Schema payload |
---|---|---|---|
Sources Flow Run Start | Sources Flow Run Start | This alert triggers when a source connection starts processing data. | { |
Sources Flow Run Success | Sources Flow Run Success | This alert triggers when data is successfully ingested from a source connection. | { |
Sources Flow Run Failure | Sources Flow Run Failure | This alert triggers when an error occurs while ingesting data from a source connection. | { |
Sources Flow Run Delay | Ingestion Delay | This alert triggers when a batch ingestion flow run takes longer than 150 minutes to process. NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
{ |
Sources Ingestion Error Rate Exceeded | Ingestion Failure | This alert triggers when the ratio of failed records to all records exceed a threshold of 0.5%. | { |
Sources Flow Run Info | Streaming Sources Completed | This alert triggers when data has completed processing from a streaming source dataflow run. | { |
If you have previously subscribed to the following alert type, you will no longer receive alerts as this alert has been deprecated:
I/O Event subscription | Alert rule | Description |
---|---|---|
Source Flow Run Delays, Failures and Errors | Lack of Ingestion | This alert sends you a message if ingestion is delayed by more than seven hours and no data gets ingested to Platform. |
The following alert rules are specific to Identity Service:
I/O Event subscription | Alert rule | Description | Schema Payload |
---|---|---|---|
Identity Service Flow Run Start | Identity Service Flow Run Start | This alert triggers when an Identity Service flow run starts processing data. In other words, ingested data is being loaded from the Data Lake into Identity Service. | { |
Identity Service Flow Run Success | Identity Service Flow Run Success | This alert triggers when data is successfully loaded from the Data Lake into Identity Service. | { |
Identity Ingestion Delays, Failures and Errors | Identity Service Flow Run Delay | This alert triggers when an Identity Service flow run takes longer than 150 minutes to process. NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
{ |
Identity Ingestion Delays, Failures and Errors | Identity Service Flow Run Failure | This alert triggers when an error occurs while ingesting data into Identity Service. NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
The following alert rules are specific to Real-Time Customer Profile:
I/O Event subscription | Alert rule | Description | Payload schema |
---|---|---|---|
Profile Flow Run Start | Profile Flow Run Start | This alert triggers when a Profile flow run starts processing data. | { |
Profile Flow Run Success | Profile Flow Run Success | This alert triggers when data is successfully loaded into Profile from the Data Lake. | { |
Profile Flow Run Delay | Profile Flow Run Delay | This alert triggers when loading data from the Data Lake into Profile takes longer than 150 minutes to process. NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
{ |
Profile Flow Run Failure | Profile Flow Run Failure | This alert triggers when an error occurs while ingesting data into Profile. | { |
The following alert rules are specific to Segmentation Service:
I/O Event subscription | Alert rule | Description | Payload Schema |
---|---|---|---|
Segment Job Start | Segment Job Start | This alert triggers when a segment evaluation job starts processing data. | { |
Segment Job Success | Segment Job Success | This alert triggers when a segment evaluation job completes successfully. | { |
Segment Job Delay | Segment Job Delay | This alert triggers when a segment evaluation jobs takes longer than 150 minutes to complete. One of the following statuses will appear: - FIRING - The condition for failure or delay has been met (Consider it in an ACTIVE state). - INACTIVE - The condition has not been met or not resolved (Consider it in a RESOLVED state). NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
{ |
Segment Job Failure | Segment Job Failure | This alert triggers when a segment evaluation job results in an error. | { |
Segment Definition Disabled | Segment Definition Disabled | This alert triggers when a segment definition is disabled due to internal error. This automatically triggers a war room for an Adobe engineering team to investigate the issue. This alert is only intended to be informative and does not require any action from you. |
The following alert rules are specific to destinations:
I/O Event subscription | Alert rule | Description | Payload schema |
---|---|---|---|
Destination Flow Run Start | Destination Flow Run Start | This alert triggers when a destination flow run starts activating a segment. | { |
Destination Flow Run Success | Destination Flow Run Success | This alert triggers when a segment is successfully activated to a destination. | { |
Destination Flow Run Delay | Destination Flow Run Delay | This alert triggers when a destination flow run takes longer than 300 minutes to activate a segment. NOTE: The delay alert evaluation will stop after 10 hours, even if the issue still exists. |
{ |
Destination Flow Run Failure | Destination Flow Run Failure | This alert triggers when an error occurs while activating a segment to a destination. | { |
Destination skippage rate exceeds threshold | Skippage rate exceeds threshold | This alert triggers when the ratio of skipped IDs to total IDs exceeds a threshold. | { |
Destination flow run info | Streaming destination completed | This alert triggers when data has completed processing from a streaming destination dataflow run | { |
The following alert rules are specific to Query Service:
I/O Event subscription | Alert rule | Description | Payload Schema |
---|---|---|---|
Query Service scheduled query start | Query Service scheduled query start | This alert triggers when a scheduled query starts running. | { |
Query Service scheduled query Success | Query Service scheduled query success | This alert triggers when a scheduled query job completes successfully. | { |
Query Run Failure | Query service scheduled query failure | This alert triggers when a scheduled query job fails. | { |
The following alert rules are specific to Audit events:
I/O Event subscription | Alert rule | Description | Payload Schema |
---|---|---|---|
Audit event info | Audience create | This alert triggers when an audience is created. | { |
Audit event info | Audience update | This alert triggers when an audience is updated. | { |
Audit event info | Audience delete | This alert triggers when an audience is deleted. | { |
Audit event info | Dataset create | This alert triggers when a dataset is created. | { |
Audit event info | Dataset update | This alert triggers when a dataset is updated. | { |
Audit event info | Dataset delete | This alert triggers when a dataset is deleted. | { |
Audit event info | Schema create | This alert triggers when a schema is created. | { |
Audit event info | Schema update | This alert triggers when a schema is updated. | { |
Audit event info | Schema delete | This alert triggers when a schema is deleted. | { |