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