Amazon CloudWatch RUM, which helps developers monitor real user interactions and diagnose front-end performance issues in web applications, now supports JavaScript source maps, enabling developers to convert minified JavaScript errors in the stack trace into readable formats for faster error resolution. With this feature, front-end developers and DevOps teams can now view searchable, human-readable JS errors and quickly identify the exact location of errors in their original source code. JavaScript errors can be difficult to debug when they are minified in the stack trace, making it hard to pinpoint the source of an issue. Now, if an error occurs in a production environment, RUM leverages customer uploaded source maps to trace it back to the original code. The added ability to search unminified stack traces in RUM events helps developers analyze trends and correlate issues across multiple sessions, enabling faster detection and prioritization of recurring errors. To unminify errors in JavaScript stack traces, customers need to enable it in the App Monitor configuration and provide the S3 URI of the bucket or folder that holds the source maps via the console or RUM APIs. These enhancements are available in all regions where CloudWatch RUM is available. Customer pay cost of storage of their source maps to Amazon S3 and for the API calls to upload and retrieve source maps as per AWS public pricing found here. See documentation to know more about the feature, or see user guide to learn how to get started with CloudWatch RUM.

Amazon CloudWatch RUM now supports Interaction to Next Paint (INP) web vital, enabling developers to measure and analyze web application responsiveness and user interaction latency.

A few weeks ago, I was reviewing the Amazon CloudWatch RUM dashboard for a web application I...

Learn how to build a secure, beginner-friendly task management application using AWS Blocks, React, and TypeScript with zero AWS infrastructure setup required for local development.

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: AWS GovCloud (US-East), and AWS GovCloud (US-West). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and HTTP errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ServiceDetail.html#ServiceDetail-clientpages. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-get-started.html. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed https://aws.amazon.com/cloudwatch/pricing/. 

Amazon CloudWatch RUM now supports iOS and Android applications, expanding real user monitoring beyond web applications. Developers and SREs can now quickly isolate mobile application issues and improve end-user experience, with visibility into performance metrics such as screen load times, crash rates, and API latencies.

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: Israel (Tel Aviv), and Asia Pacific (Hong Kong). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and Http errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ServiceDetail.html#ServiceDetail-clientpages. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-get-started.html. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed https://aws.amazon.com/cloudwatch/pricing/.  

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: Asia Pacific (Malaysia), and Canada West (Calgary). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and HTTP errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ServiceDetail.html#ServiceDetail-clientpages. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM-get-started.html. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed https://aws.amazon.com/cloudwatch/pricing/. 

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: AWS GovCloud (US-East), and AWS GovCloud (US-West). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and HTTP errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, CloudWatch Application Signals. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the RUM User Guide. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed here.

I am a 4th-year CSE student preparing for a DevOps career and sharing my learning journey across AWS, Linux, Docker, Git, CI/CD, Kubernetes, and cloud technologies.

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: Israel (Tel Aviv), and Asia Pacific (Hong Kong). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and Http errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, CloudWatch Application Signals. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the RUM User Guide. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed here.

Amazon CloudWatch RUM, which enables customers to monitor their web applications by collecting client side performance and error data in real time, is additionally available in the following AWS Regions starting today: Asia Pacific (Malaysia), and Canada West (Calgary). CloudWatch RUM provides curated dashboards for web application performance experienced by real end users including anomalies in page load steps, core web vitals, and JavaScript and HTTP errors across different geolocations, browsers, and devices. Custom events and metrics sent to CloudWatch RUM can be easily configured to monitor specific parts of the application for real user interactions, troubleshoot issues, and get alerted for anomalies. CloudWatch RUM comes integrated with the application performance monitoring (APM) capability, CloudWatch Application Signals. As a result, client-side data from your application can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to address the root cause. To get started, see the RUM User Guide. Usage of CloudWatch RUM is charged on the number of collected RUM events, which refers to each data item collected by the RUM web client, as detailed here.

Amazon CloudWatch RUM now allows customers to monitor multiple top-level domains (TLDs), and second-level domains (SLDs) using a single App Monitor unifying real user monitoring across multiple domains in CloudWatch RUM. Customers can now specify a list of domains and also use wildcards for TLDs to monitor all their front-end applications together. This enhancement is useful for web applications that need to be accessible from different domains due to various reasons such as user locations, domain migrations, or any other development needs. This enhancement simplifies observability for applications accessed from multiple domains by displaying all real user data of the application on a single RUM dashboard. Customers can now monitor different SLDs, such as example.com and another.com, without creating separate monitors for each domain. They can also track applications deployed across multiple TLDs, such as example.com, and example.co.uk, helping monitoring performance across regions. Wildcard support for TLDs allows customers even more flexibility to monitor all variants of a domain, such as example.* or example.co.*, without manually specifying each one. Additionally, subdomain wildcards, which is already supported, continue to allow monitoring across multiple subdomains like *.example.com. These capabilities simplifies monitoring websites that operate in multiple regions, manage domain transitions during SLD migrations, and other development needs by consolidating data in a single place. This feature is now available in all AWS commercial regions where CloudWatch RUM is available. See documentation to know more about the feature, or see the one observability workshop to learn how to get started with CloudWatch RUM.

Amazon CloudWatch RUM now supports iOS and Android applications, expanding real user monitoring beyond web applications. Developers and SREs can now quickly isolate mobile application issues and improve end-user experience, with visibility into performance metrics such as screen load times, crash rates, and API latencies. CloudWatch RUM for mobile uses the OpenTelemetry (OTEL) standard to send spans and events. The service captures mobile spans such as application startup time, screen load time and backend network calls. It also captures events including crashes, and ANRs/AppHangs to provide rich troubleshooting insights on the CloudWatch console. You can perform impact analysis for specific errors or crashes, drill down to correlated telemetry, and filter by location, device type, operating system, and app versions to quickly identify root causes. Mobile telemetry integrates with application metrics, traces, logs, web RUM monitoring, and synthetic monitoring in CloudWatch Application Signals to speed up troubleshooting and reduce application disruption. CloudWatch RUM support for iOS and Android is available in all AWS Commercial Regions where web monitoring is available. To learn more, see pricing, getting started for Android and iOS, and documentation.

Amazon CloudWatch RUM, which helps developers monitor real user interactions and diagnose front-end performance issues in web applications, now supports JavaScript source maps, enabling developers to convert minified JavaScript errors in the stack trace into readable formats for faster error resolution. With this feature, front-end developers and DevOps teams can now view searchable, human-readable JS errors and quickly identify the exact location of errors in their original source code. JavaScript errors can be difficult to debug when they are minified in the stack trace, making it hard to pinpoint the source of an issue. Now, if an error occurs in a production environment, RUM leverages customer uploaded source maps to trace it back to the original code. The added ability to search unminified stack traces in RUM events helps developers analyze trends and correlate issues across multiple sessions, enabling faster detection and prioritization of recurring errors. To unminify errors in JavaScript stack traces, customers need to enable it in the App Monitor configuration and provide the S3 URI of the bucket or folder that holds the source maps via the console or RUM APIs. These enhancements are available in all regions where CloudWatch RUM is available. Customer pay cost of storage of their source maps to Amazon S3 and for the API calls to upload and retrieve source maps as per AWS public pricing found here. See documentation to know more about the feature, or see user guide to learn how to get started with CloudWatch RUM.  

「This Month in AWS Observability」最新号へようこそ。今回は、この6月に Amazon CloudWatch と AI 駆動型オペレーション全般で発表された新機能をご紹介します。CloudWatch でネイティブな OpenTelemetry メトリクスと PromQL クエリが一般提供（GA）となり、より深い統計・構造化分析のための 23 個の新しい Logs Insights コマンドがローンチされ、CloudWatch RUM に Session Replay が登場し、 AWS DevOps Agent では MCP および Agent-to-Agent プロトコルをサポートするカスタム SRE エージェントがリリースされました。EKS クラスター全体で GPU コストを配賦する場合も、実際のセッション再生でフロントエンドの問題をデバッグする場合も、チームのランブックを自律型 SRE エージェントに組み込む場合も、役立つ情報が見つかるはずです。

Discover how to design scalable, decoupled, and fault-tolerant event-driven data processing pipelines using AWS Lambda, Amazon EventBridge, and DynamoDB.

「This Month in AWS Observability」最新号へようこそ。今回は、この6月に Amazon CloudWatch と AI 駆動型オペレーション全般で発表された新機能をご紹介します。CloudWatch でネイティブな OpenTelemetry メトリクスと PromQL クエリが一般提供（GA）となり、より深い統計・構造化分析のための 23 個の新しい Logs Insights コマンドがローンチされ、CloudWatch RUM に Session Replay が登場し、 AWS DevOps Agent では MCP および Agent-to-Agent プロトコルをサポートするカスタム SRE エージェントがリリースされました。EKS クラスター全体で GPU コストを配賦する場合も、実際のセッション再生でフロントエンドの問題をデバッグする場合も、チームのランブックを自律型 SRE エージェントに組み込む場合も、役立つ情報が見つかるはずです。

Introduction Welcome to the latest edition of This Month in AWS Observability, featuring what’s new across Amazon CloudWatch and AI-driven operations this June! Native OpenTelemetry metrics with PromQL querying is now generally available in CloudWatch, 23 new Logs Insights commands launched for deeper statistical and structured analysis, Session Replay now in CloudWatch RUM, and AWS [...]