Skip to main content
Version: NG-2.15

Browser RUM Alerts

Page-High Network Time Alert​

This alert is triggered when the network time for a page exceeds the defined threshold, impacting page load performance and user experience. High network time can be caused by slow server responses, high latency, or network congestion.

  • Alert Configuration:
    • Alert Metric: Network Time
    • Aggregation: Single Value
    • Group By: Application Name, URL
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when network time exceeds 500ms, indicating potential performance degradation affecting user experience.

By monitoring network time, teams can quickly identify and resolve slow response times, ensuring seamless page performance and optimizing end-user experience.

API Transaction Volume Alert​

This alert monitors the transaction volume of API requests and triggers notifications when the request count deviates significantly from the historical average. A sudden increase or decrease in transaction volume may indicate anomalies, traffic spikes, or backend failures.

  • Alert Configuration:
    • Alert Metric: API Request Count
    • Aggregation: Count
    • Group By: Application Name
    • Evaluation Period: 15 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when the current transaction volume is 20% lower than the historical average for the same time last week.
      • Warning: Triggered when the current transaction volume is 20% higher than the historical average.

By continuously tracking API transaction volume, teams can proactively identify unexpected surges or drops in API usage, enabling quick troubleshooting and resource allocation adjustments.

Page-High XHR Response time Alert​

This alert detects high response times for XHR (XMLHttpRequest) requests, which can indicate slow API responses, backend processing delays, or network congestion affecting user experience.

  • Alert Configuration:
    • Alert Metric: XHR Response Time
    • Aggregation: Duration (milliseconds)
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Level:
      • Critical: Triggered when the XHR response time exceeds 500ms for a monitored page.

Monitoring XHR response time helps teams quickly identify slow API calls, optimize performance, and improve the responsiveness of web applications.

API Historical Request Rate Alert​

This alert detects a drop in API request rate compared to historical trends. A significant decrease may indicate backend issues, reduced traffic, or system failures affecting user requests.

  • Alert Configuration:
    • Alert Metric: P90 Request Rate
    • Aggregation: 90th percentile
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Level:
      • Critical: Triggered when the request rate drops 30% below the average request rate for the same time last week.

By tracking API request trends, teams can quickly detect unexpected traffic drops, investigate potential system failures, and take proactive measures to maintain application reliability.

API Historical Error Rate Alert​

This alert notifies when the API error rate in the last 5 minutes exceeds 10% and is at least 5% higher than the average error rate of the last hour. It helps in detecting sudden spikes in API failures, allowing teams to take immediate corrective actions.

  • Alert Configuration:
    • Alert Metric: Failure Percentage
    • Aggregation: Historical Comparison
    • Group By: Application
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Historical Comparison Alerting: Critical

This alert helps identify unexpected increases in API failure rates, ensuring timely troubleshooting and maintaining service reliability.

Page-High Browser rendering time Alert​

This alert identifies high browser rendering times, which can significantly impact page load speed and user experience. A delay in rendering can be caused by heavy scripts, inefficient DOM updates, or rendering bottlenecks.

  • Alert Configuration:
    • Alert Metric: Browser Rendering Time
    • Aggregation: 90th percentile
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Level:
      • Critical: Triggered when browser rendering time exceeds 500ms, indicating potential frontend performance issues.

By monitoring rendering time, teams can identify bottlenecks, optimize rendering processes, and enhance page responsiveness for an improved user experience.

API Average duration Alert​

This alert is triggered when the average API response duration in the last 10 minutes exceeds 30% of the average duration from the past 1 hour. A sudden increase in response time may indicate backend inefficiencies, resource bottlenecks, or increased load on the system.

  • Alert Configuration:
    • Alert Metric: API Average Duration
    • Aggregation: Average
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Level:
      • Critical: Triggered when the API response duration increases by more than 30% compared to the historical average.

By monitoring API duration trends, teams can proactively address slowdowns, optimize performance, and ensure seamless user experience.

Page-Web Vitals - Cumulative Layout Shift Alert​

This alert is triggered when the Cumulative Layout Shift (CLS) score of a page exceeds the standard threshold, impacting page stability and user experience. CLS measures unexpected layout shifts, which can lead to poor usability and frustration for users.

  • Alert Configuration:
    • Alert Metric: Cumulative Layout Shift (CLS)
    • Aggregation: Latest Value
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when CLS score exceeds 0.25, indicating significant layout shifts.
      • Warning: Triggered when CLS score exceeds 0.1, suggesting potential layout instability.

By monitoring CLS, teams can identify and fix layout shift issues, ensuring a stable and user-friendly browsing experience.

Page-Web Vitals - First Input Delay Alert​

This alert is triggered when the First Input Delay (FID) time exceeds the standard threshold, indicating delayed responsiveness of a webpage. FID measures the time taken by the browser to respond to a user's first interaction, such as clicking a button or tapping a link.

  • Alert Configuration:
    • Alert Metric: First Input Delay (FID)
    • Aggregation: Latest Value
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when FID exceeds 300ms, indicating severe delays in user interaction responsiveness.
      • Warning: Triggered when FID exceeds 100ms, suggesting minor performance degradation.

By monitoring First Input Delay, teams can optimize website responsiveness, ensuring a smooth and interactive user experience.

Page-Overall Load time High for Page Alert​

This alert is triggered when the 95th percentile (P95) of page load time exceeds the defined threshold, indicating slower page loading performance. High load times can negatively impact user experience, engagement, and conversion rates.

  • Alert Configuration:
    • Alert Metric: P95 Latency
    • Aggregation: 95th Percentile
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when page load time exceeds 500ms, indicating significant delays affecting users.

By monitoring Overall Load Time, teams can identify slow-loading pages, optimize web performance, and ensure a seamless user experience.

API Error rate greater than 5% Alert​

This alert is triggered when the error rate of API requests exceeds 5% in the last 10 minutes. A high error rate can indicate service instability, failed transactions, or potential backend issues, impacting the application's reliability.

  • Alert Configuration:
    • Alert Metric: Error Rate
    • Aggregation: Percentage of Failed Requests
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when the error rate is between 5% and 10%, signaling a potential issue.
      • Critical: Triggered when the error rate exceeds 10%, indicating a major service disruption.

By monitoring API error rates, teams can quickly detect anomalies, troubleshoot failures, and prevent service degradation, ensuring a seamless user experience.

API high duration for historical average Alert​

This alert is triggered when the 90th percentile (P90) of API response duration in the last 10 minutes exceeds 30% more than the historical P90 duration of the last week at the same time. This helps in identifying service slowdowns and performance regressions.

  • Alert Configuration:
    • Alert Metric: Response Duration (P90)
    • Aggregation: 90th Percentile
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when the response duration increases by 30% or more compared to the same period last week.

By tracking historical trends, this alert helps teams detect slowdowns, optimize API performance, and prevent service degradation, ensuring a smooth user experience.

Page-Web Vitals - Largest Contentful Paint is High Alert​

This alert is triggered when the Largest Contentful Paint (LCP) time exceeds defined performance thresholds, indicating slow page rendering. LCP measures the time taken for the largest visible content (image or text block) to load in the viewport, directly impacting user experience.

  • Alert Configuration:
    • Alert Metric: Largest Contentful Paint (LCP)
    • Aggregation: Time in milliseconds (ms)
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when LCP exceeds 4000ms.
      • Warning: Triggered when LCP exceeds 2500ms but is below 4000ms.

By tracking LCP spikes, this alert helps teams optimize rendering performance, enhance user experience, and ensure fast-loading web pages.

Page-High Server Time Alert​

This alert is triggered when the server response time for a web page exceeds a predefined threshold, indicating potential backend performance issues. High server time can lead to increased page load times, negatively impacting user experience and application responsiveness.

  • Alert Configuration:
    • Alert Metric: Server Response Time
    • Aggregation: Time in milliseconds (ms)
    • Group By: Application Name
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when server time exceeds 500ms

By continuously monitoring server response times, this alert helps teams identify performance bottlenecks, optimize backend processing, and ensure efficient application performance.

API High Duration Alert​

This alert is triggered when the 90th percentile of API response duration in the last 10 minutes exceeds 500ms, indicating potential performance bottlenecks in API processing. Monitoring high-duration API calls helps identify latency issues, optimize service response times, and enhance user experience.

  • Alert Configuration:
    • Alert Metric: API Response Duration (P90)
    • Aggregation: 90th percentile
    • Group By: Application Name
    • Evaluation Period: 10 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Critical: Triggered when the 90th percentile duration exceeds 500ms

By proactively detecting slow API response times, this alert enables teams to pinpoint latency issues, troubleshoot backend inefficiencies, and maintain optimal API performance.

Page-Load time high for Geo location Alert​

This alert is triggered when the 95th percentile (P95) of page load time exceeds 5 seconds for a specific geographic location. Monitoring page load times across different regions helps identify slow-performing locations, optimize content delivery, and enhance the user experience.

  • Alert Configuration:
    • Alert Metric: Page Load Time (P95 Latency)
    • Aggregation: 95th percentile
    • Group By: City / Geo Location
    • Evaluation Period: 5 minutes
    • Alert Execution Period: 5 minutes
    • Severity Levels:
      • Warning: Triggered when P95 load time exceeds 5 seconds

This alert helps identify regional performance issues, allowing teams to fine-tune CDN configurations, optimize network routing, and improve page responsiveness for users in affected locations.