CloudWatch Application Signals now supports Runtime Metrics for .NET Applications
Today, AWS is announcing the general availability of runtime metrics for .NET applications in Amazon CloudWatch Application Signals, an OpenTelemetry (OTel)-compatible application performance monitoring (APM) feature in CloudWatch. Without requiring any source code changes, you can now collect runtime metrics such as Garbage Collection and Heap usage from .NET applications and correlate with application metrics, traces, and logs for applications running across EKS, EC2, ECS and on-premise servers.
Runtime metrics enable real-time monitoring of your application’s resource consumption, such as memory and CPU usage. Now, for .NET applications, developers and SREs can determine whether anomalies in runtime metrics affect key application metrics—such as errors, latency, and throughput. For example, they can identify if a service latency spike is a result of an increase in garbage collection pauses by viewing these metric graphs side by side. Additionally you will be able to identify thread contention, track memory allocation patterns, and pinpoint memory or CPU spikes that may lead to application slowdown, impacting end-user experience.
Runtime metrics support is available for Java, Python and now .NET applications across all regions Application Signals is available in.
See documentation to learn more about the standard and runtime metrics collected by Application Signals. Don’t forget to opt in to the new, cost-effective pricing for Application Signals. For more details, visit the Amazon CloudWatch pricing page and look for the “Application Signals (including complete visibility into application transaction spans)” section.