Once you’ve integrated with AWS CloudWatch, you have access to all metrics for AWS RUM, which engages in real user monitoring to gather and view client-side information regarding the functionality of your web application from actual user sessions in close to real time.
See all AWS integrations.
To verify metrics are reporting, search for the metrics in the Metric details section of the Settings page.
The following table shows the CloudWatch RUM metrics ingested by Cloud Observability.
| Metric Name | Unit | Description |
|---|---|---|
| aws.rum.http_status_code_count | count | The count of HTTP responses in the application by their response status code. |
| aws.rum.js_error_count | count | The count of JavaScript error events ingested. |
| aws.rum.navigation_frustrated_count | count | The count of navigation occurrences that last longer than the 8000-millisecond threshold that causes frustration. |
| aws.rum.navigation_satisfied_count | count | The count of navigational events whose length is shorter than the 2000 ms Apdex aim. |
| aws.rum.navigation_tolerated_count | count | The count of navigational occurrences that last between 2000 and 8000 milliseconds. |
| aws.rum.performance_resource_duration | milliseconds | The amount of duration of a resource event. |
| aws.rum.performance_navigation_duration | milliseconds | The amount of duration of a navigation event. |
| aws.rum.rum_event_payload_size | bytes | The size of every event ingested by CloudWatch RUM. |
| aws.rum.session_count | count | The count of session start events ingested by the app monitor. |
| aws.rum.web_vitals_cumulative_layout_shift | none | Tracks the value of the cumulative layout shift events. |
| aws.rum.web_vitals_first_input_delay | milliseconds | The value of the first input delay events. |
| aws.rum.web_vitals_largest_contentful_paint | milliseconds | The value of the largest contentful paint events. |
See also
Updated Dec 7, 2022