AWS AmazonCloudWatch documentation change
Summary
Expanded CloudWatch RUM documentation to include mobile application monitoring capabilities (Android/iOS), updated terminology from 'events' to 'telemetry data', restructured content about client implementation (dependency injection vs JavaScript snippet), added mobile SDK references, removed detailed performance considerations section, and simplified pricing/content organization.
Security assessment
Changes focus on feature expansion (mobile support) and documentation restructuring. No mention of vulnerabilities, security patches, or access control changes. Removed performance considerations section contained operational guidance but no security-specific content. References to data retention/CloudWatch Logs remain unchanged regarding security implications.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.md index 08b9f5a50..c23057f9d 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.md @@ -7 +7 @@ -With CloudWatch RUM, you can perform real user monitoring to collect and view client-side data about your web application performance from actual user sessions in near real time. The data that you can visualize and analyze includes page load times, client-side errors, and user behavior. When you view this data, you can see it all aggregated together and also see breakdowns by the browsers and devices that your customers use. +With CloudWatch RUM, you can perform real user monitoring to collect and view client-side data about your web and mobile application performance from actual user sessions in near real time. For Web applications, you can analyze page load times, client-side errors, and user behavior. For Mobile applications, you can monitor screen load times, app launch times, network errors, crashes, and platform-specific issues such as Android Application Not Responding (ANR) and iOS App Hangs. When you view this data, you can see it all aggregated together and also see breakdowns by device types, operating systems, and other characteristics of your application usage. @@ -9 +9 @@ With CloudWatch RUM, you can perform real user monitoring to collect and view cl -You can use the collected data to quickly identify and debug client-side performance issues. CloudWatch RUM helps you visualize anomalies in your application performance and find relevant debugging data such as error messages, stack traces, and user sessions. You can also use RUM to understand the range of end user impact including the number of users, geolocations, and browsers used. +You can use the collected data to quickly identify and debug client-side performance issues. CloudWatch RUM helps you visualize anomalies in your application performance and find relevant debugging data such as error messages, stack traces, and user sessions. You can also use RUM to understand the range of end user impact including the number of users, geolocations, and browsers/devices used. @@ -11,17 +11 @@ You can use the collected data to quickly identify and debug client-side perform -End user data that you collect for CloudWatch RUM is retained for 30 days and then automatically deleted. If you want to keep the RUM events for a longer time, you can choose to have the app monitor send copies of the events to CloudWatch Logs in your account. Then, you can adjust the retention period for that log group. - -To use RUM, you create an _app monitor_ and provide some information. RUM generates a JavaScript snippet for you to paste into your application. The snippet pulls in the RUM web client code. The RUM web client captures data from a percentage of your application's user sessions, which is displayed in a pre-built dashboard. You can specify what percentage of user sessions to gather data from. - -CloudWatch RUM is integrated with [Application Signals](./CloudWatch-Application-Monitoring-Sections.html), which can discover and monitor your application services, clients, Synthetics canaries, and service dependencies. Use Application Signals to see a list or visual map of your services, view health metrics based on your service level objectives (SLOs), and drill down to see correlated X-Ray traces for more detailed troubleshooting. To see RUM client page requests in Application Signals, turn on X-Ray active tracing by [creating an app monitor](./CloudWatch-RUM-get-started-create-app-monitor.html), or [manually configuring the RUM web client](./CloudWatch-RUM-configure-client.html). Your RUM clients are displayed on the [Application Map](./ServiceMap.html) connected to your services, and in the [Service detail](./ServiceDetail.html) page of the services they call. - -The RUM web client is open source. For more information, see [CloudWatch RUM web client](https://github.com/aws-observability/aws-rum-web). - -**Performance considerations** - -This section discusses the performance considerations of using CloudWatch RUM. - - * **Load performance impact** — The CloudWatch RUM web client can be installed in your web application as a JavaScript module, or loaded into your web application asynchronously from a content delivery network (CDN). It does not block the application’s load process. CloudWatch RUM is designed to have no perceptible impact on application load time. - - * **Runtime impact** — The RUM web client performs processing to record and dispatch RUM data to the CloudWatch RUM service. Because events are infrequent and the amount of processing is small, CloudWatch RUM is designed for there to be no detectable impact to the application’s performance. - - * **Network impact** — The RUM web client periodically sends data to the CloudWatch RUM service. Data is dispatched at regular intervals while the application is running, and also immediately before the browser unloads the application. Data sent immediately before the browser unloads the application are sent as beacons, which, are designed to have no detectable impact on the application’s unload time. +End user data that you collect for CloudWatch RUM is retained for 30 days and then automatically deleted. If you want to keep the RUM telemetry data for a longer time, you can choose to have the app monitor send copies of the telemetry to CloudWatch Logs in your account. Then, you can adjust the retention period for that log group. @@ -28,0 +13 @@ This section discusses the performance considerations of using CloudWatch RUM. +To use RUM, you create an _app monitor_ and provide some information. RUM generates a code snippet that you can use to add a dependency injection into your application. The snippet pulls in the RUM client code as needed. The RUM client captures data from a percentage of your application's user sessions, which is displayed in a pre-built dashboard. You can specify what percentage of user sessions to gather data from. @@ -29,0 +15 @@ This section discusses the performance considerations of using CloudWatch RUM. +CloudWatch RUM is integrated with [Application Signals](./CloudWatch-Application-Monitoring-Sections.html), which can discover and monitor your application services, clients, Synthetics canaries, and service dependencies. Use Application Signals to see a list or visual map of your services, view health metrics based on your service level objectives (SLOs), and drill down to see correlated X-Ray traces for more detailed troubleshooting. To see RUM client page requests in Application Signals, turn on X-Ray active tracing when [creating an app monitor](./CloudWatch-RUM-get-started-create-app-monitor.html). For web applications, you can also enable this by [manually configuring the RUM web client](./CloudWatch-RUM-configure-client.html). Your RUM clients are displayed on the [Application Map](./ServiceMap.html) connected to your services, and in the [Service detail](./ServiceDetail.html) page of the services they call. @@ -30,0 +17 @@ This section discusses the performance considerations of using CloudWatch RUM. +The RUM clients are open source. For more information, see [CloudWatch RUM web client](https://github.com/aws-observability/aws-rum-web), the [AWS Distro for OpenTelemetry (ADOT) Android SDK](https://github.com/aws-observability/aws-otel-android), and [AWS Distro for OpenTelemetry (ADOT) iOS SDK](https://github.com/aws-observability/aws-otel-swift). @@ -34 +21 @@ This section discusses the performance considerations of using CloudWatch RUM. -With CloudWatch RUM, you incur charges for every RUM event that CloudWatch RUM receives. Each data item collected using the RUM web client is considered a RUM event. Examples of RUM events include a page view, a JavaScript error, and an HTTP error. You have options for which types of events are collected by each app monitor. You can activate or deactivate options to collect performance telemetry events, JavaScript errors, HTTP errors, and X-Ray traces. For more information about choosing these options, see [Creating a CloudWatch RUM app monitor](./CloudWatch-RUM-get-started-create-app-monitor.html) and [Information collected by the CloudWatch RUM web client](./CloudWatch-RUM-datacollected.html). For more information about pricing, see [Amazon CloudWatch Pricing](https://aws.amazon.com/cloudwatch/pricing/). +For information about pricing, see [Amazon CloudWatch Pricing](https://aws.amazon.com/cloudwatch/pricing/). @@ -111,35 +97,0 @@ CloudWatch RUM is currently available in the following Regions: -###### Topics - - * [IAM policies to use CloudWatch RUM](./CloudWatch-RUM-permissions.html) - - * [Set up an application to use CloudWatch RUM](./CloudWatch-RUM-get-started.html) - - * [Using resource-based policies with CloudWatch RUM](./CloudWatch-RUM-resource-policies.html) - - * [Configuring the CloudWatch RUM web client](./CloudWatch-RUM-configure-client.html) - - * [Enabling unminification of JavaScript error stack traces](./CloudWatch-RUM-JavaScriptStackTraceSourceMaps.html) - - * [Regionalization](./CloudWatch-RUM-Regionalization.html) - - * [Use page groups](./CloudWatch-RUM-page-groups.html) - - * [Specify custom metadata](./CloudWatch-RUM-custom-metadata.html) - - * [Send custom events](./CloudWatch-RUM-custom-events.html) - - * [Viewing the CloudWatch RUM dashboard](./CloudWatch-RUM-view-data.html) - - * [CloudWatch metrics that you can collect with CloudWatch RUM](./CloudWatch-RUM-metrics.html) - - * [Data protection and data privacy with CloudWatch RUM](./CloudWatch-RUM-privacy.html) - - * [Information collected by the CloudWatch RUM web client](./CloudWatch-RUM-datacollected.html) - - * [Manage your applications that use CloudWatch RUM](./CloudWatch-RUM-manage.html) - - * [Troubleshooting CloudWatch RUM](./CloudWatch-RUM-troubleshooting.html) - - - - @@ -154 +106 @@ Performing safe canary updates -IAM policies to use CloudWatch RUM +Set up a mobile application to use CloudWatch RUM