While testing AWS CloudWatch Container Insights with Enhanced Observability I felt the urge to provide a configuration with a better fit to our needs. Reading through the linked aws-observability best-practices guides, a section about "Cost savings with Container Insights on Amazon EKS" was very interesting. In particular the subsection called: "Customize Metrics and Dimensions".
The metric_declaration solution presented there seems easy to understand and very straight forward.
However, nowadays, after the release of CloudWatch Container Insights with Enhanced Observability, it seems to me the presented guides are out of date.
Why? Because I believe if one follows the suggested installation method (EKS add-on), the otel-agent-conf documented in the guide is not used anymore.
But, looking at the log of the deployed cloudwatch-agent, it still uses the awsemfexporter. Hence, I believe it should be possible to use the described metric_declaration:
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/5ccdbe08c6a2a43b7c6c7f9c0031a4b0348394a9/exporter/awsemfexporter/README.md#metric_declaration
I would be very thankful if someone could help me understand how we could move forward here. Because the number of metrics Container Insights gathers which are not useful for use is very hight, therefore creating unnecessary hight costs.
AWS OFFICIALUpdated 2 months ago
Additionally, I found the following 2-4 year old issues/requests on GitHub:
It seems like this functionality would be highly appreciated.