Skip to main content
Version: NG-2.16

Mobile RUM Alerts

MRUM ANR Rate Alert​

This alert is triggered when the App Not Responding (ANR) rate for a monitored mobile application exceeds the defined threshold within the last 10 minutes. A high ANR rate indicates that the app is becoming unresponsive for users, which can severely affect user experience and retention.

Alert Configuration:

  • Alert Metric: ANR Rate Percentage (anr_rate_percentage)
  • Aggregation: Latest Value
  • Group By: Application Name
  • Evaluation Period: 10 minutes
  • Alert Execution Period: 5 minutes
  • Severity Levels:
    • Warning: Triggered when ANR rate is ≥ 5% and < 10%
    • Critical: (If configured) Triggered when ANR rate exceeds 10%

By monitoring ANR rate, teams can quickly detect unresponsive behavior in mobile apps, identify root causes, and take corrective actions to maintain application stability and user satisfaction.

MRUM Error Rate Alert​

This alert is triggered when the error rate for a monitored mobile application exceeds the defined threshold within the last 10 minutes. A high error rate can indicate recurring issues such as failed API calls, screen-level exceptions, or other operational problems that degrade the user experience.

  • Alert Configuration:
    • Alert Metric: Error Rate Percentage (error_rate_percentage)
    • Aggregation: Latest Value
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when the error rate is ≥ 5% and < 10%
      • Critical: (If configured) Triggered when the error rate exceeds 10%

By monitoring the application’s error rate, teams can quickly identify spikes in failures, investigate underlying issues, and resolve problems before they significantly impact users.

MRUM API Historical Error Rate Alert​

This alert is triggered when the current API error rate for a mobile application is significantly higher than its historical value for the same time during the past hour. This helps detect sudden performance degradations or system issues that may not be visible through absolute thresholds alone.

  • Alert Configuration:
    • Alert Metric: Failure Rate (failure_rate)
    • Aggregation: Historical Comparison
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Historical Comparison Window: Same time in the last 1 hour (and optionally last 1 week for reference)
    • Severity Levels:
      • Critical: Triggered when the error rate exceeds the configured percentage above the historical average.

By comparing the current API failure rate against historical patterns, teams can proactively identify anomalies, investigate potential backend or network issues, and take corrective action before widespread impact occurs.

MRUM API High Duration Alert​

This alert is triggered when API response times exceed a defined threshold and are significantly higher compared to historical values for the same application. It compares current performance against both the last one hour and the same time in the previous week to detect anomalies and performance degradation.

  • Alert Configuration:
    • Alert Metric: API Response Duration (high_duration_api)
    • Aggregation: P90 Duration
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Historical Comparison Windows:
      • Last 1 hour
      • Same time in the last week
      • Top 5 slowest APIs (by P95 duration)
    • Severity Levels:
      • Critical: Triggered when the current API duration is above the threshold and exceeds both the one-hour and one-week historical averages by 30% or more.
      • Warning: Triggered when the current duration exceeds either the one-hour or one-week historical average by 30%, or when it is simply above the set threshold.

By monitoring both real-time and historical API duration trends, this alert helps teams detect slowdowns early, identify affected APIs, and take action to maintain optimal application responsiveness.

MRUM API Historical Request Rate Alert​

This alert detects a drop in API request rate compared to historical trends. It compares the current request rate with both the previous hour and the same time in the previous week. If the rate falls below 30% of historical values, it signals a possible performance issue, traffic drop, or backend failure.

  • Alert Configuration:
    • Alert Metric: API Request Rate (P90_Request_Rate)
    • Aggregation: 90th Percentile
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Historical Comparison Windows:
      • Last 1 hour
      • Same time in the last week
    • Severity Levels:
      • Critical: Triggered when the current request rate is 30% or more below both the one-hour and one-week historical averages.

By monitoring API request rates against historical baselines, this alert helps teams quickly identify sudden drops in traffic, investigate potential system outages or reduced usage, and take corrective action to maintain service availability.

MRUM API Transaction Volume Alert​

This alert monitors the total volume of API requests and compares it to historical trends. A sudden increase or decrease in request volume can signal traffic spikes, unusual user behavior, or possible backend issues.

  • Alert Configuration:
    • Alert Metric: API Request Count (request_count)
    • Aggregation: Count
    • Group By: Application Name
    • Evaluation Period: 15 minutes
    • Alert Execution Period: 5 minutes
    • Historical Comparison Windows:
      • Same time yesterday
      • Same time last week
    • Severity Levels:
      • Critical: Triggered when the current request volume is 20% or more below both the previous day and last week’s averages.
      • Warning: Triggered when the current request volume is 20% or more above both the previous day and last week’s averages.

By monitoring API transaction volumes against historical baselines, teams can detect unusual drops or surges in usage, investigate anomalies, and quickly respond to potential performance or availability issues.

MRUM Screen-Load Time High for Geo Location Alert​

This alert detects when the screen load time is unusually high for users from a specific geographic location. High load times in certain regions may indicate network latency, CDN configuration issues, or localized infrastructure problems affecting user experience.

  • Alert Configuration:
    • Alert Metric: Screen Load Time (high_latency_screen)
    • Aggregation: 95th Percentile (P95)
    • Group By: Application Name, Geo Location
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when the P95 screen load time for a geo location is greater than or equal to 1 second.

By tracking high screen load times per geographic location, teams can identify region-specific performance bottlenecks, optimize delivery paths, adjust CDN configurations, and ensure a consistent experience for users worldwide.

MRUM Crash Rate Alert​

This alert monitors the crash rate of a mobile application and triggers when it exceeds defined thresholds. High crash rates indicate stability issues that can lead to poor user experience and reduced app usage.

  • Alert Configuration:
    • Alert Metric: Crash Rate (crash_rate_percentage)
    • Aggregation: Percentage
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when crash rate is greater than or equal to 5% but below 10%.
      • Critical: Triggered when crash rate is greater than or equal to 10%.

By monitoring crash rates, teams can quickly detect stability issues, investigate the root cause, and take corrective action to maintain a reliable and smooth mobile application experience.

MRUM API Error Rate Greater Than 5% Alert​

This alert monitors API error rates in a mobile application and triggers when they exceed defined thresholds. High API error rates can indicate backend issues, failed transactions, or service instability that may impact user experience.

  • Alert Configuration:
    • Alert Metric: API Error Rate (apis_above_5_percent)
    • Aggregation: Percentage of Failed Requests
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when the error rate is greater than or equal to 5% but below 10%.
      • Critical: Triggered when the error rate is greater than or equal to 10%.

By tracking API error rates, teams can quickly identify anomalies, troubleshoot failures, and restore service stability, ensuring reliable application performance.