Released On
Bug Fixes
🐞 [Logs] Only add to cache if log stream is created 🐞 by @jefchien in #1566
This change fixes a bug in v1.300052.0 where if agents installed in a fleet/cluster are writing to log streams in the same log group, there could be a race condition where one agent creates the log group and the others detect the presence of the log group falsely as a success and caches the same, preventing them from trying to re-create the log stream and successfully publishing logs.
🐞 [Core] Take entity data into account for payload size 🐞 by @varunch77 in #1483
This change fixes a bug between v1.300049.1 and v1.300052.0 where in some edge cases, the agent can miscalculate the overall size of a request and not batch the metrics effectively.
Enhancements
💡 [Application Signals] Add endpoint slice watcher 💡 by @pxaws in #1528
The startup logic in Application Signals was previously calling expensive list API calls to the /pods endpoint on the K8s API Server, overloading the control plane for large clusters. With this optimization, we switched to a less expensive list/watch mechanism for /endpointslices, retrieving a lot less information that is actually required for the Application Signals experience.
💡 [Logs] Reduce PutRetentionPolicy calls by checking existing policy 💡 by @movence in #1545
Previously, the agent would make a PutRetentionPolicy API call for every log group every time it restarted, thus causing throttling issues. With this enhancement, the agent first checks if the Retention Policy is already set by calling DescribeLogGroup and only sets it if required. It also now does this asynchronously and with a jitter & exponential backoff.
💡 [Related telemetry] Scrape auto scaling group attributes from resource metrics 💡 by @zhihonl in #1521
Previously, if IMDS tags are disabled, the agent would not set the ASG on the entity even though it can be retrieved through ectagger using the Describe API. We now retrieve ASG from ec2tagger for entity even when IMDS tags are not enabled
💡 [Related telemetry] Add entity processor to the otlp metrics and logs pipeline 💡 by @duhminick in #1504
Extends support for setting entities for the OTLP flows both in the metrics and logs section when running on EKS to provide an even richer Related telemetry experience
💡 [Core] Changing log level of cert watcher from error to debug 💡 by @mitali-salvi in #1531
Reduce verbosity of a non-impacting warning to reduce clutter
💡 [Core] Fix EKS cluster detection 💡 by @musa-asad in #1532
The agent previously relied on the existence of aws-auth config map to know if it was running on EKS. With the launch of EKS access entries, aws-auth is considered deprecated. So we now switched to a better mechanism to inspect the issue field in the service account when determining if we are running on EKS
Full Changelog: v1.300052.0...v1.300053.0
