However, it appears despite my ConfigMap being updated to have Enhanced Observability turned on, the CW agent is not recognising it. Taking a look at the config translator config, none of the if enhancedContainerInsightsEnabled { conditions succeed. So, no enhanced metrics are added to the awsemf/containerinsights exporter config.
Describe the bug Recently, the eks-charts team supported passing
enhanced_container_insights
into the CW Agent ConfigMap (https://github.com/aws/eks-charts/pull/1041)However, it appears despite my ConfigMap being updated to have Enhanced Observability turned on, the CW agent is not recognising it. Taking a look at the config translator config, none of the
if enhancedContainerInsightsEnabled {
conditions succeed. So, no enhanced metrics are added to theawsemf/containerinsights
exporter config.Is anyone able to reproduce this issue on EKS?
Steps to reproduce Use
v.0.0.10
for Enhanced Observability metrics in EKS - https://github.com/aws/eks-charts/pull/1041What did you expect to see? Enhanced Observability metrics being pushed to CW / Agent's OTEL config updated when
enhanced_container_insights=true
What did you see instead? Default Kubernetes Container Insights config being loaded.
What version did you use? Version:
v1.300032.3b392
What config did you use? Config: (e.g. the agent json config file)
Environment OS: (e.g., "Ubuntu 20.04")
Additional context
ConfigMap
Cloudwatch agent pod logs