Releases: aws/amazon-cloudwatch-agent
v1.300061.0
Released On
🐞 Bug Fixes 🐞
-
[Configuration] Append logic for merging JVM/OTLP configurations fix
The CWA was unable to correctly append JVM/OTLP configurations when using the config (append) action. This change addresses this issue by allowing customers to append multiple configurations of this type. @lisguo #1870 -
[Configuration] Add support for EC2 metadata as dimensions
Fixed an issue where the agent was unable to use the ${aws: formatting to substitute dimensions with EC2 metadata information or tags. @lisguo #1876 -
[Configuration] Add support for EC2 tags as dimensions for host metrics
Fixed an issue where the agent only supports raw key/value pairs for the append_dimensions section of the host metrics config. This fix allows the agent to support dynamic AutoScalingGroup dimension using EC2 metadata. @lisguo #1892 -
[Logs] Memory leak fix when using publish_multi_logs flag
This bug fix addressing a memory leak issue when using the publish_multi_logs flag with dynamically determined log destinations in CloudWatch Logs. This was due to the agent not correctly closing open goroutines for associated log files. @dricross #1848 -
[Contrib] Fixed messaging system logic
Bug fix to facilitate the proper linking of cross service traces @sky333999 amazon-contributing/opentelemetry-collector-contrib#368 -
[Agent] Windows startup issue fix
There was an error in the Agent where it would fail to start on windows on stderr. This change updates the agent control scripts to address the issue. @movence #1906
💡 Enhancements 💡
-
[Packaging] Updated OTeL JMX jar used by the agent
The CWA was using a custom build of the OpenTelemetry JMX Metrics Gatherer JAR. There has been several newer versions released upstream that contain bug fixes for JMX metrics etc. This change removes the custom build in favor of using the upstream version. This also reduced the size of the agent by 200MB. -
[Agent] IPv6 Support on EC2
Adds CloudWatch Agent support for IPv6 on EC2 INSTANCES @Paramadon #1871
Full Changelog: v1.300060.0...v1.300061.0
v1.300060.0
Released On
🐞 Bug Fixes 🐞
- [Logs] Fixed detection of truncated log files to prevent missing or duplicate log entries
- [Prometheus] Fixed Prometheus metrics being sent to undefined log streams in EKS when configured alongside Kubernetes/ECS
- [Processors] Fixed transform processor missing 'error mode' that cause silent failures during metric transformations
- Fixing CWA error_mode bug in addon v4.2.0 by @Paramadon in #1837
- [OTLP] Fixed receiver port conflict issues
- [ContainerInsights] Fixed duplicate metrics collection from Kueue controller by limiting to single collector pod
- Update contrib components to v0.0.0-20250916160455-365e3e3baf3a by @sky333999 in #1865
- Update contrib components to v0.0.0-20250916235509-415059d978ca by @sky333999 in #1866
- [Debian] Debian package restarts amazon-cloudwatch-agent after upgrade
🚀 New Features 🚀
- [ContainerInsights] Added Ingress, PersistentVolume and PersistentVolumeClaim metrics
- [Metrics] Added support for exponential histograms
💡 Enhancements 💡
- [Agent] RPM size reduction by optimizing helper binaries
- Refactor helper binaries to save 161MB of disk space when the agent is installed and reduce RPM by 48MB by @chadpatel in #1454
New Contributors
Full Changelog: v1.300059.0...v1.300060.0
v1.300059.0
Released On
🐞Bug Fixes🐞
- [ApplicationSignals] Fix race conditions in applicationsignals processor by @bjrara in #1758
- [Logs] Update state when batch dropped by @duhminick in #1789
- [Logs] Revert "Add default log publishing concurrency (#1770)" by @jefchien in #1819
- [JMX] Fix infinite loop bug when java is missing by @dricross in amazon-contributing/opentelemetry-collector-contrib#343
- [JMX] Fix permissions check for non-linux users by @lisguo in amazon-contributing/opentelemetry-collector-contrib#344
🚀New Features 🚀
- [Logs/Windows] Add windows event id filtering to CWAgent by @Paamicky in #1737
- [Logs/Windows] Add windows event regex filtering to CWAgent by @Paamicky in #1764
- [Logs/Windows] Add event ID and regex features to CWAgent configuration wizard by @Paamicky in #1774
- [Metrics/Memory] Add mem_shared metric to CloudWatch Agent by @ola-amr in #1792
- [Metrics/NVME] Adding NVME Instance Store Metrics by @Paramadon in #1810
- [ContainerInsights] Add UltraServer support for CloudWatch agent by @petruanica in #1571
- [ContainerInsights] Add new Tensor Core and GPU capacity metrics by @tudor-manea in #1814
- [ContainerInsights] Add Neuron Core and EFA capacity metrics by @sky333999 in #1820
💡Enhancements💡
- [Logs] Zero-allocation optimization for sendLine and readLine by @duhminick in #1803
- [Logs] Dynamic reader buffer for tail by @duhminick in #1809
- [ApplicationSignals] Add aws.remote.resource.account.* attributes to Application Signals EMF logs by @bjrara in #1791
New Contributors
- @Paamicky made their first contribution in #1737
- @ola-amr made their first contribution in #1792
- @petruanica made their first contribution in #1571
- @tudor-manea made their first contribution in #1814
Full Changelog: v1.300058.0...v1.300059.0
v1.300058.0
Released On
🚀New Features 🚀
- [ContainerInsights] Ability to set CollectionRole for Container Insights by @sky333999 in #1766
💡Enhancements💡
- [Logs] Adjust log input and output plugins to support 1MB log lines and resolve issues with truncation logic by @TravisStark in #1762
- [Logs] Add default log publishing concurrency by @jefchien in #1770
- [Logs] Small refactor for Windows Event Log gap handling by @duhminick in #1777
- [Logs] Restore and send gaps for Windows events by @duhminick in #1747
Full Changelog: v1.300057.0...v1.300058.0
v1.300057.0
Released On
🐞Bug Fixes🐞
- [ApplicationSignals] Fix concurrency bug by @bjrara in #1704
- [ContainerInsights] Fix grouping for container insights metrics for mixed metric types by @lisguo in amazon-contributing/opentelemetry-collector-contrib#320
- [ContainerInsights] Aggregrate neuroncore utilization across core/device pairs by @spanaik in #1713
- [Logs] Fix concurrent map write by @chadpatel in #1707
- [Logs] Reduce DescribeLogGroup throttling by @duhminick in #1717
💡Enhancements💡
- [Related Telemetry] Allow service and environment configuration for OTLP in EC2 by @zhihonl in #1700
- [Prometheus] mTLS support for Target Allocator by @musa-asad in #1510
- [OpenTelemetry] Update fallback for OTel config flag by @jefchien in #1697
- [Logs] Improved log state management by @jefchien in #1718 and @duhminick in #1721
- [ApplicationSignals] Add support for deployment.environment.name by @thpierce in #1722
- [OpenTelemetry] Bump OTel dependencies to v0.124.1 by @Paramadon in #1694
- [Core] Bump Go version to 1.24.4 by @lisguo in #1725
Full Changelog: v1.300056.0...v1.300057.0
v1.300056.0
Released On
🐞Bug Fixes🐞
- [ContainerInsights] Fix endpoint slice to capture service name instead of slice name by @sky333999 in amazon-contributing/opentelemetry-collector-contrib#314
- [EMF] Fix output of count/sum metrics for detailed summary metrics by @dricross in amazon-contributing/opentelemetry-collector-contrib#313
- [Metrics/NVIDIA GPU] Update v12 XML schema to include missing power_draw metrics by @movence in #1679
🚀New Features 🚀
- [ContainerInsights] Ingest EBS NVME metrics exposed by aws-ebs-csi-driver by @zhihonl in #1625 and amazon-contributing/opentelemetry-collector-contrib#309
💡Enhancements💡
- [Application Signals] Enable customizable attribute copying from resources to metrics for better metric organization by @thpierce in #1676
- [Explore Related] Add automatic EC2 metadata enrichment for OpenTelemetry data collection by @zhihonl in #1665
Full Changelog: v1.300055.1...v1.300056.0
v1.300055.2
Released On
Bug Fixes
🐞 [ContainerInsights] Fix endpoint slice to capture service name instead of slice name 🐞 by @sky333999 in amazon-contributing/opentelemetry-collector-contrib#314
This change fixes a bug between v1.300054.0 and v1.300055.1 where the agent would incorrectly send the Service as the name of the endpoint slice as opposed to the name of the service itself on the Container Insights metrics.
v1.300054.1
Released On
Enhancements
💡 [Core] Go1.24 bump by @Paramadon in #1623 💡
The same artifacts as v1.300054.0 but built with Go 1.24.
v1.300055.1
Released On
Enhancements
💡 [Core] Go1.24 bump by @Paramadon in #1623 💡
The same artifacts as v1.300055.0 but built with Go 1.24.
v1.300055.0
Released On
Bug Fixes
🐞 [Prometheus/AMP] Add deltatocumulativeprocessor for AMP destinations 🐞 by @dricross in #1624
When using CWAgent to scrape Prometheus metrics and publish to Amazon Managed Prometheus (AMP), the agent would previously drop any non-cumulative delta metrics, leading to a potential loss in observability. This bug fixes the issue by inserting a delta to cumulative processor in the pipeline such that we no longer drop these metrics.
🐞[Application Signals] Fix service ip to workload mapping in an edge case 🐞 by @pxaws in #1644
An edge case was introduced in v1.300053.0 where a K8s Service backed by one pod that is terminated can trigger a race condition resulting in the agent not mapping the pod's IP to the corresponding application/workload - thus breaking the Application Signals topology & experience. This fixes the race condition by accounting for delayed termination of pods when populating the PodIP <-> Service cache.
Enhancements
💡 [Explore Related] Support entity for OTLP custom metrics / Add service entity support for EMF exporter 💡by @musa-asad in #1529
CWAgent now supports attaching Entity information (namespace, node name & application/workload) for OTLP custom metrics sent to it. This expands the coverage of Exploring Related telemetry to use cases utilizing the agent's standalone OTLP plugin for metrics (even when Application Signals is not being used).
💡 [Explore Related] Implement Kubernetes Metadata Extension 💡 by @musa-asad in #1605
In order to facilitate attaching entity for use cases outside of Application Signals, CWAgent needs the ability to map a Source IP back to the corresponding application/workload. This change introduces a new re-usable extension that extracts the logic to map a Source IP to a workload into a common place that can then be used for Application Signals, Explore Related & other use cases in the future.
💡 [Explore Related] Add platform type for Container Insights in EKS 💡by @zhihonl in #1638
Container logs published to Container Insights log groups cannot be distinguished for EKS vs native K8s today and this results in Container Insights metrics not being properly correlated to Container Insights application logs. With this enhancement, the agent now sets the Platform Type (EKS vs native K8s) on the log events to facilitate correct correlation between metrics & logs for customers leveraging Explore Related.
💡 [Core] Reduce noisy warning log in CI podresourcesstore / Reduce noisy logs with prometheus receiver 💡 by @okankoAMZ in amazon-contributing/opentelemetry-collector-contrib#300 and by @movence in amazon-contributing/opentelemetry-collector-contrib#297
These enhancements reduce the verbosity of noisy logs printed by the agent in scenarios when Enhanced Container Insights is enabled and also on non-GPU Kubernetes clusters. These logs were previously polluting the agent logs with noise, leading to confusion when triaging genuine issues.
Full Changelog: v1.300054.0...v1.300055.0