AWS AmazonCloudWatch documentation change
Summary
Restructured dashboard documentation with separate sections for Web and Mobile application monitoring. Added detailed metrics descriptions for mobile apps including crashes, ANRs/App Hangs, and session telemetry. Expanded Apdex score explanation with calculation formula.
Security assessment
Changes focus on feature documentation improvements for monitoring application performance metrics and error types. No evidence of addressing vulnerabilities or security incidents. While crash/error monitoring could help identify potential stability issues, this is operational rather than security-focused documentation.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-view-data.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-view-data.md index bc46ef32d..79278e37c 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-view-data.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-view-data.md @@ -4,0 +5,2 @@ +Web Application DashboardMobile Application Dashboard + @@ -7 +9 @@ -CloudWatch RUM helps you collect data from user sessions about your application's performance, including page load times, Apdex score, browsers and devices used, geolocation of user sessions, and sessions with errors. All of this information is displayed in a dashboard. +CloudWatch RUM helps you collect data from user sessions about your application's performance, including load times, Apdex score, device information, geolocation of user sessions, and sessions with errors. All of this information is displayed in a dashboard. @@ -9 +11 @@ CloudWatch RUM helps you collect data from user sessions about your application' -###### To view the RUM dashboard +To view the RUM dashboard: @@ -15,7 +16,0 @@ CloudWatch RUM helps you collect data from user sessions about your application' -The **Overview** tab displays information collected by one of the app monitors that you have created. - -The top row of panes displays the following information for this app monitor: - - * Number of page loads - - * Average page load speed @@ -23 +17,0 @@ The top row of panes displays the following information for this app monitor: - * Apdex score @@ -25 +18,0 @@ The top row of panes displays the following information for this app monitor: - * Status of any alarms associated with the app monitor @@ -27 +20 @@ The top row of panes displays the following information for this app monitor: -The application performance index (Apdex) score indicates end users' level of satisfaction. Scores range from 0 (least satisfied) to 1 (most satisfied). The scores are based on application performance only. Users are not asked to rate the application. For more information about Apdex scores, see [How CloudWatch RUM sets Apdex scores](./CloudWatch-RUM-apdex.html). +The RUM console displays a list view of all your app monitors. The **Platform** column indicates whether each app monitor is for Web, Android, or iOS applications. Select an app monitor to access detailed views with **Performance** , **Errors** , **Sessions** , **Metrics** and **Configuration** tabs. @@ -29 +22 @@ The application performance index (Apdex) score indicates end users' level of sa -Several of these panes include links that you can use to further examine the data. Choosing any of these links displays a detailed view with **Performance** , **Errors** , **HTTP requests** , **Sessions** , **Events Browsers & Devices**, and **User Journey** tabs at the top of the display. +## Web Application Dashboard @@ -31 +24 @@ Several of these panes include links that you can use to further examine the dat - 3. To focus further, choose the **List view** tab and then choose the name of the app monitor that you want to focus on. This displays the following tabs for the chosen app monitor. +When you select a web application monitor, you'll see the following tabs: @@ -51 +44,47 @@ If you narrow the scope to a single browser, you see the data broken down by bro - 4. (Optional) On any of the first six tabs, you can choose the **Pages** button and select a page or page group from the list. This narrows down the displayed data to a single page or group of pages of your application. You can also mark pages and page groups in the list as favorites. + * The **Metrics** tab displays all default CloudWatch metrics published by your app monitor, including performance web vitals, error metrics (JavaScript errors, HTTP errors/faults), volume, user flow and apdex metrics. If you created extended metrics for your application, the tab also includes a subset of these metrics in the extended metrics section. This subset includes metrics of type PageViewCount, PerformanceNavigationDuration, Http4xxCount, Http5xxCount and JsErrorCount. The dashboard shows three metric variations per metric type. Since these are CloudWatch metrics, you can also export this tab to your own dashboard using the **Add to dashboard** option and update it to include more metrics. + + + + +(Optional) On any of the first six tabs, you can choose the **Pages** button and select a page or page group from the list. This narrows down the displayed data to a single page or group of pages of your application. You can also mark pages and page groups in the list as favorites. + +## Mobile Application Dashboard + +When you select a mobile application monitor, you'll see the following tabs: + + * The **Performance** tab provides insights into the performance of your mobile application including screen load times, app launch times (cold and warm), performance metrics, and Apdex scores over time. The detailed view breaks down performance by screen names, OS versions, app versions, devices, and countries. Clicking a screen load time, app launch time, or location datapoint in the chart will open the diagnostic panel on the right that provides further insights relevant to the datapoint consisting the most recent correlated sessions and links to the **Sessions** tab for troubleshooting. + +On this tab you can also toggle the view between **Screen loads** , **App launches** , and **Location** to see more details about application performance. + +The tab also features the application performance index (Apdex) score which indicates end users' level of satisfaction. Scores range from 0 (least satisfied) to 1 (most satisfied). The scores are based on application performance only. For more information about Apdex scores, see . + + * The **Errors** tab breaks down application issues in three categories: Network Errors, Crashes, and ANRs (Android)/App Hangs (iOS). The **Network Errors** tab has a line chart showing network latency, client errors (4xx status code), and server errors (5xx status code). Clicking on a data point for any of these lines in the chart will open the diagnostic panel. The bottom table lists the 100 most common network routes. Clicking on a radio button will filter the line chart by the network route selected. + +Similarly, the **Crashes** and **ANRs/App Hangs** tabs show a line series for the count of each error, and these are intractable. The bottom table displays the most common top crash message or ANR/App Hang stack trace. Clicking on a radio button will filter the chart, and clicking the error message will show the complete stack trace. + + * The **Sessions** tab displays a table that lists all sessions in descending chronological order. At the bottom, a waterfall visualization shows all telemetry for the selected session, helping you track user interactions and identify performance issues. Each row in the waterfall can be selected to open the diagnostic panel. For HTTP requests, you'll see a **traceId** that links to the Traces console. + +For HTTP requests with non-2xx status codes, crashes, or ANRs (Android)/ App Hangs (iOS), the diagnostic panel includes an **Exception** tab with the stack trace. The **View** button in the waterfall provides quick access to this information. + + * The **Metrics** tab displays all default CloudWatch metrics published by your app monitor, including performance metrics (screen load times, cold app launch times), error metrics (crashes, ANRs/App Hangs, HTTP errors/faults), volume and apdex metrics. If you created extended metrics for your application, the tab also includes a subset of these metrics in the extended metrics section. This subset includes metrics of type ScreenLoadTime, ScreenLoadCount, CrashCount, Http4xxCount, Http5xxCount, ANRCount/AppHangCount, ColdLaunchTime and WarmLaunchTime. The dashboard shows three metric variations per metric type. Since these are CloudWatch metrics, you can also export this tab to your own dashboard using the **Add to dashboard** option and update it to include more metrics. + + * The **Configuration** tab provides access to your app monitor's general settings and configuration details. You can also access the **Code snippets** tab which contains instructions for instrumenting your mobile application with the ADOT SDK, including both Manual and Zero-Code instrumentation options. + + + + +### How CloudWatch RUM sets Apdex scores + +Apdex (Application Performance Index) is an open standard that defines a method to report, benchmark, and rate application response time. An Apdex score helps you understand and identify the impact on application performance over time. + +The Apdex score indicates the end users' level of satisfaction. Scores range from 0 (least satisfied) to 1 (most satisfied). The scores are based on application performance only. Users are not asked to rate the application. + +Each individual Apdex score falls into one of three thresholds. Based on the Apdex threshold and actual application response time, there are three kinds of performance, as follows: + + * **Satisfied** — The actual application response time is less than or equal to the Apdex threshold. For CloudWatch RUM, this threshold is 2000 ms or less. + + * **Tolerable** — The actual application response time is greater than the Apdex threshold, but less than or equal to four times the Apdex threshold. For CloudWatch RUM, this range is 2000—8000 ms. + + * **Frustrating** — The actual application response time is greater than four times the Apdex threshold. For CloudWatch RUM, this range is over 8000 ms. + + @@ -53,0 +93 @@ If you narrow the scope to a single browser, you see the data broken down by bro +The total 0-1 Apdex score is calculated using the following formula: @@ -54,0 +95 @@ If you narrow the scope to a single browser, you see the data broken down by bro +`(positive scores + tolerable scores/2)/total scores * 100` @@ -64 +105 @@ Send custom events -How CloudWatch RUM sets Apdex scores +CloudWatch metrics that you can collect with CloudWatch RUM