Configuring ASM Alert Thresholds for Active-Active Monitoring Environments

Products

• DX SaaS
• DX Operational Observability
• DX Application Performance Management

Issue/Introduction

Symptoms

• Alerts for ASM monitors trigger incorrectly in active-active monitoring configurations.
• Incident generation occurs for partial failure counts instead of total expected failure thresholds.
• Threshold breaches do not match the configured period over threshold settings when multiple agents are involved.

Environment

• DX Operational Observability (DX SaaS)
• ASM (Application Synthetic Monitoring)
• Active-Active agent configuration

Cause

1. Alert thresholds are incorrectly configured for the aggregate number of monitored failures across multiple parallel agents. When an alert is set to trigger based on a specific number of total failures, but the monitoring environment uses multiple agents, the threshold must account for the aggregate count across all agents to avoid premature or incorrect alert triggering.
2. Ensure to upgrade to latest version and you are using either Event Streaming or Direct ingestion to ensure accurate data reporting and evaluation:

• Configure DX ASM Monitor Extension with Event Stream
• Synthetics Direct Ingestion

Resolution

1. Navigate to the Alert Configuration for the specific ASM monitor.
2. Review the "Periods Over Threshold" and "Observed Periods" settings.
3. Calculate the total expected failures across all active agents. If monitoring 2 failures across 2 agents, ensure the threshold is set to the aggregate count (e.g., 4) rather than the individual agent count.
4. Adjust the "Periods Over Threshold" to ensure alerts only trigger when the total aggregate threshold is consistently breached.
5. Save the updated configuration and validate the behavior during a scheduled maintenance window.

Additional Information

• If additional assistance is required, refer to Contact Broadcom Support or Creating and Managing Broadcom Support Cases.