AWS AmazonCloudWatch documentation change
Summary
Expanded documentation for CloudWatch Application Signals with new sections about features, supported languages/architectures/regions, dynamic service grouping, deployment tracking, and automated audit findings. Restructured content with clearer organization.
Security assessment
Changes primarily add feature descriptions and operational monitoring capabilities without addressing specific security vulnerabilities. The 'automated audit findings' section describes performance analysis rather than security audits. No mention of security patches, vulnerabilities, or access controls. Cross-account observability mentions monitoring but doesn't discuss security implications of cross-account access.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.md index 33ae49042..5b608a323 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.md @@ -4,0 +5,2 @@ +Features + @@ -7 +9,12 @@ -Use CloudWatch Application Signals to automatically instrument your applications on AWS so that you can monitor current application health and track long-term application performance against your business objectives. Application Signals provides you with a unified, application-centric view of your applications, services, and dependencies, and helps you monitor and triage application health. +CloudWatch Application Signals helps you monitor and improve application performance on AWS. It automatically collects data from your applications running on services like Amazon EC2, Amazon ECS, and Lambda. You can use CloudWatch Application Signals for the following: + + * Monitor application health in real time + + * Track performance against business goals + + * View relationships between services and dependencies + + * Quickly identify and resolve performance issues + + + @@ -19,0 +33,12 @@ Use CloudWatch Application Signals to automatically instrument your applications +**Supported languages and architectures** + +Application Signals supports Java, Python, Node.js, and .NET applications. + +Application Signals is supported and tested on Amazon EKS, Amazon ECS, and Amazon EC2. On Amazon EKS clusters, it automatically discovers the names of your services and clusters. On other architectures, you must supply the names of services and environments when you enable those services for Application Signals. + +The instructions for enabling Application Signals on Amazon EC2 should work on any architecture that supports the CloudWatch agent and AWS Distro for OpenTelemetry. However, the instructions have not been tested on architectures other than Amazon ECS and Amazon EC2. + +**Supported Regions** + +Application Signals is supported in every commercial Region except for Canada West (Calgary). + @@ -21,0 +47,2 @@ Use CloudWatch Application Signals to automatically instrument your applications + * Features + @@ -55 +82 @@ Use CloudWatch Application Signals to automatically instrument your applications -**Use Application Signals for daily application monitoring** +## Features @@ -57 +84 @@ Use CloudWatch Application Signals to automatically instrument your applications -Use Application Signals within the CloudWatch console, as part of daily application monitoring: + * **Use Application Signals for daily application monitoring** – Use Application Signals within the CloudWatch console, as part of daily application monitoring: @@ -63,4 +90 @@ Use Application Signals within the CloudWatch console, as part of daily applicat - 3. If new services have been deployed or dependencies have changed, open the [Service Map](./ServiceMap.html) to inspect your application topology. See a map of your applications that shows the relationship between clients, Synthetics canaries, services, and dependencies. Quickly see SLI health, view key metrics such as call volume, fault rate, and latency, and drill down to see more detailed information in the [Service detail](./ServiceDetail.html) page. - - - + 3. If new services have been deployed or dependencies have changed, open the [Application Map](./ServiceMap.html) to inspect your application topology. See a map of your applications that shows the relationship between clients, Synthetics canaries, services, and dependencies. Quickly see SLI health, view key metrics such as call volume, fault rate, and latency, and drill down to see more detailed information in the [Service detail](./ServiceDetail.html) page. @@ -74,3 +98 @@ It is not necessary to enable Application Signals to use CloudWatch Synthetics, -**Application Signals cross-account** - -With Application Signals cross-account observability, you can monitor and troubleshoot your applications that span multiple AWS accounts within a single Region. + * **Application Signals cross-account** – With Application Signals cross-account observability, you can monitor and troubleshoot your applications that span multiple AWS accounts within a single Region. @@ -80,2 +101,0 @@ You can use Amazon CloudWatch Observability Access Manager to set up one or more -###### Required resources - @@ -91,0 +112 @@ For proper functionality of Application Signals cross-account observability, ens + * **Dynamic service grouping and filtering** – Group and filter services with Application Signals' dynamic grouping capabilities. Automatically aggregate metrics and SLIs of services within groups, allowing you to start from a group view and dive deep into specific problematic areas. Application Signals automatically discovers and groups services based on their configuration and relationship. You can also create custom groups that align with your business needs. For example, you can group services by business units, teams, or critical tiers. View consolidated performance metrics, track group-level SLIs, and quickly identify non-performing services. Using grouping, you can organize your large-scale distributed services into logical groups that align with your operational needs and simplifies monitoring them especially during incidents. @@ -92,0 +114 @@ For proper functionality of Application Signals cross-account observability, ens +The system analyzes the service dependency graph and creates groups where the root node (a service with no upstream dependencies) becomes the group name. All services that depend on this root service, either directly or indirectly, are automatically included in the group. For example, if Service A calls Service B, which in turn calls Service C, all three services will be grouped together with Service A as the group name since it's the root of the dependency chain. This automatic grouping mechanism provides a natural way to visualize and manage related services based on their actual runtime interactions and dependencies. @@ -93,0 +116 @@ For proper functionality of Application Signals cross-account observability, ens +Create custom groupings using AWS tags or OpenTelemetry attributes that align with your team structure, business domains, or operational requirements. Custom groupings enable you to organize services according to your specific monitoring and troubleshooting workflows. For more information, see [Configuring custom groups](./ServiceMap.html#Application-Map-Configure-Custom-Groups). @@ -95 +118 @@ For proper functionality of Application Signals cross-account observability, ens -**Supported languages and architectures** + * **Last deployment tracking** – You can track latest deployment tracking for each service and its dependencies, which provides crucial context for troubleshooting without any manual configuration or setup. Identify and monitor the last deployment time for each service and dependencies, providing crucial context for operational analysis and troubleshooting without additional configuration or setup requirements. Correlate deployment times with performance changes, detect deployment-related issues, and maintain a comprehensive deployment history across your application landscape. This feature helps teams quickly determine if recent deployments contributed to service degradation and supports faster incident resolution. @@ -97 +120 @@ For proper functionality of Application Signals cross-account observability, ens -Application Signals supports Java, Python, Node.js, and .NET applications. +Application Signals automatically correlates deployment events with performance metrics, helping you quickly identify whether recent deployments are contributing to service issues. The system tracks deployment timing and provides visual indicators when performance changes align with deployment activities. @@ -99 +122,3 @@ Application Signals supports Java, Python, Node.js, and .NET applications. -Application Signals is supported and tested on Amazon EKS, Amazon ECS, and Amazon EC2. On Amazon EKS clusters, it automatically discovers the names of your services and clusters. On other architectures, you must supply the names of services and environments when you enable those services for Application Signals. +Maintain a comprehensive view of deployment activities across your application landscape. View deployment frequency, timing patterns, and success rates to optimize your deployment strategies and identify potential risk factors. + + * **Automated audit findings** – Discover critical insights through Application Signals' automated audit findings such as EMF logs of Application Signals RED metrics, traces, and application logs. The service analyzes your applications to report observations, including finding top outliers who contributed to the latency, faults, or errors, finding issues started from dependency services, and finding the detailed error information from application logs to help better understand the root cause. The audit system employs advanced analytics to detect patterns, highlight resource inefficiencies, and suggest root causes. Findings are prioritized based on severity and potential business impact, enabling teams to focus on the most critical issues first. Get actionable recommendations for improving service reliability, and performance without manual analysis. @@ -101 +125,0 @@ Application Signals is supported and tested on Amazon EKS, Amazon ECS, and Amazo -The instructions for enabling Application Signals on Amazon EC2 should work on any architecture that supports the CloudWatch agent and AWS Distro for OpenTelemetry. However, the instructions have not been tested on architectures other than Amazon ECS and Amazon EC2. @@ -103 +126,0 @@ The instructions for enabling Application Signals on Amazon EC2 should work on a -**Supported Regions** @@ -105 +127,0 @@ The instructions for enabling Application Signals on Amazon EC2 should work on a -Application Signals is supported in every commercial Region except for Canada West (Calgary).