Skip to main content
Version: NG-2.15

Browser Journey Alerts

Synthetic Browser Journey Monitoring comes with a suite of seven pre-configured alerts designed to provide actionable insights into browser workflows. These alerts enable proactive monitoring and troubleshooting of user journeys, ensuring reliability, efficiency, and exceptional user experiences. With Synthetic Browser Journey Monitoring Alerts, you can swiftly identify potential issues, mitigate disruptions, and optimize browser workflows for seamless application performance.

High Journey Duration Alert​

Triggered when the 95th percentile (P95) duration for a journey exceeds a defined threshold (e.g., 5 seconds). This alert focuses on identifying journeys with consistently high response times.

  • Alert Metric: P95 Latency
  • Threshold: P95 > 5s
  • Group By: Journey Name
  • Evaluation Period: 5 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: UNHEALTHY status with high P95 duration

High Error Percentage Alert​

Triggered when the Error % exceeds 10% for a journey. This alert helps identify workflows with repeated failures, ensuring prompt investigation.

  • Alert Metric: Error Percentage
  • Threshold: Error % > 10%
  • Group By: Journey Name
  • Evaluation Period: 5 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: UNHEALTHY status with a high error percentage

Stale Journey Alert​

Triggered when a journey has not run for a prolonged period (e.g., more than 12 hours). This alert ensures that all critical workflows are regularly monitored and tested.

  • Alert Metric: Time Since Last Run
  • Threshold: Time Since Last Run > 12 hours
  • Group By: Journey Name
  • Evaluation Period: 5 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Stale status with no recent runs

High Journey Error Rate Alert​

Triggered when a journey experiences repeated failures over multiple runs, leading to an Error % greater than 5%. This alert helps detect persistent issues affecting user workflows.

  • Alert Metric: Error Percentage
  • Threshold: Error % > 5%
  • Group By: Journey Name
  • Evaluation Period: 5 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Multiple UNHEALTHY runs

Inconsistent Journey Latency Alert​

Triggered when the P95 latency fluctuates by more than 20% between runs. This alert identifies performance inconsistency across journey executions.

  • Alert Metric: P95 Latency
  • Threshold: Variance > 20%
  • Group By: Journey Name
  • Evaluation Period: 5 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Healthy status but fluctuating latency

Journey Completion Alert​

Triggered when the Total Runs for a journey fall below a defined threshold (e.g., fewer than 2 runs in the last 10 minutes). This ensures that all workflows are actively monitored.

  • Alert Metric: Total Runs
  • Threshold: Total Runs < 2
  • Group By: Journey Name
  • Evaluation Period: 10 minutes
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Low Total Runs

Historical Error Rate Alert​

Triggered when the Error % for a journey exceeds the historical average error rate by 20%. This alert tracks performance trends over time.

  • Alert Metric: Error Percentage
  • Threshold: Error % > Historical Average + 20%
  • Group By: Journey Name
  • Evaluation Period: 1 hour
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Sudden increase in errors compared to historical data

Historical Duration Comparison Alert​

Triggered when the P95 duration for a journey deviates by more than 15% from its historical average duration for the last week. This ensures consistent performance over time.

  • Alert Metric: P95 Latency
  • Threshold: P95 > Historical Average + 15%
  • Group By: Journey Name
  • Evaluation Period: 1 week
  • Alert Execution Period: 5 minutes
  • Trigger Condition: Higher-than-usual duration

This alert identifies significant deviations in journey completion rates and helps mitigate potential risks.