The CloudWatch Pricing page in" Example 13 Container Insights for Amazon EKS and Kubernetes with & without enhanced observability" expalins that when using "with enhanced observability" I will be charged based on the number of observations.
I know that I can get the "Container Insights with enhanced observability" using the "amazon-cloudwatch-observability" eks addon
Now, can I get the same effect with the ADOT eks add-on? and how? Specially I want to get the pricing based on number of observations.
AWS 공식업데이트됨 9달 전
This is a very interesting question and I would like to see an answer as well. My personal motivation would be to use the much better configuration and metrics filtering possibilities of adot compared to the "amazon-cloudwatch-observability" eks addon.
Yesterday, I tested the EKS ADOT add-on with the
awscontainerinsightreceiver& theawsemfexporter.The new Container Insights dashboard was showing some of the metrics. I believe some of the ADOT performance logs do match the Enhanced Observability standard.
However, I was noticing that the cost structure changed completely. Cost Explorer was not showing
CW:ObservationUsageanymore but a lot moreDataProcessing-Bytes&CW:MetricMonitorUsage. Google "told me" that this is caused by CW Custom Metrics.So, the "Observation-based" pricing is somehow connected to the tool being used but how?