Keine Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- Wie behebe ich Setup-Probleme, wenn ich Fluent Bit mit Container Insights für Amazon EKS integriere?AWS OFFICIALAktualisiert vor einem Jahr
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
& theawsemf
exporter.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:ObservationUsage
anymore 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?