cloudwatch bill with lambda is high. Any insights into why this is the case and how to control costs?
A customer is concerned about their CloudWatch bill. They are using lambda, and logging to CloudWatch. Reviewing their costs, it seems like the following metric is causing the high bill: "GetMetricData" Both "CW:GMD-Metrics ($)" and "CW:MetricMonitorUsage"
Has anyone else seen high bills rates with these metrics and lambda? Any insights are appreciated.
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
If you need a indepth analysis of what is happening we need to do a API Caller Analysis for GetMetricData. One thing to keep in mind is that GetMetricData is billed by number of metrics requested and not by API calls. 1 ) You need to identify the resources 2) look at what calls are being made 3) then Metrics vs requested per call
Does the customer using any monitoring service (Say - Data Dog) .
I would suggest to open a support case . So that engineer will be able to go deep dive to the API calls and will give you the exact metrics
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 3 Jahren- AWS OFFICIALAktualisiert vor 6 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren