- Newest
- Most votes
- Most comments
Hi,
CloudWatch automatically collects basic metrics about almost all AWS service you use and there is no way to disable it. What is the problem? What do you want to get?
There are lot of metrics getting tracked like HealthyStateRouting, UnHealthyStateRouting etc. We dont require it for test env and it is adding lot more costs too for us.
We are having the daily cost of ~$50 for CW:MetricMonitorUsage (Metrics). How can we reduce it?
As mentioned in the AWS documentation, many AWS services automatically publish a default set of metrics to CloudWatch (known as basic monitoring) with no charge to customers, including ELB and Elasticache.
Have you analyzed CloudWatch cost and usage data with Cost Explorer to check if they are related to custom metrics, detailed monitoring, embedded metrics, alarms o custom dashboards? Those features generate costs.
we got to know that MetricStorage:AWS/Logs-EMF this is adding more cost. how can I check from where it is getting used?
It seems that you are sending embedded metric format logs from your application or a CloudWatch agent. The following AWS documentation page describes how to find those metrics on CloudWatch console.
ELB and ElastiCache metrics are basic monitoring metrics.
There is no option to disable this metric.
By the way, there is no charge for basic monitoring metrics, so there is no need to think about cost.
https://aws.amazon.com/jp/cloudwatch/pricing/
There are lot of metrics getting tracked like for ELB inside Cloudwatch -> Metrics - HealthyStateRouting, UnHealthyStateRouting etc. We dont require it for test env and it is adding lot more costs too for us.
The ELB metrics you have described fall under the "Basic Monitoring Metrics" listed in the free section of the following document, so there is no charge for them. https://aws.amazon.com/cloudwatch/pricing/?nc1=h_ls
Ok then We are having the daily cost of ~$50 for CW:MetricMonitorUsage (Metrics). How can we reduce it?
If you are using custom metrics as described in the documentation, you will be charged a fee. Make sure you are not using custom metrics.
Relevant content
- asked 8 months ago
- asked 6 years ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
we got to know that MetricStorage:AWS/Logs-EMF this is adding more cost. how can I check from where it is getting used?