How do I reduce "CW:GMD-Metrics" costs?

Question

I've noticed a cost labeled as "CW:GMD-Metrics" in my AWS Cost Explorer. I believe this is related to Amazon CloudWatch custom metrics, specifically the ingestion and storage of granular metric data.

I'm looking for advice on how to drill down and find optimization opportunities to reduce these costs.

Here's what I've considered so far:

*  Evaluating the necessity of each custom metric.
* Adjusting the metric resolution.
* Optimizing metric storage and retention periods.

I'd appreciate any further suggestions, especially on how to identify the major cost contributors and best practices for optimizing CloudWatch custom metrics usage. If anyone has had experience reducing "CW:GMD-Metrics" costs or has any insights, please share!

Thank you in advance for your help!

Answer

You are on the right track . first step to understand what you were charged for and why -
Review your AWS Cost and Usage reports to understand your CloudWatch charges. Look for charges for the following services.

*  Custom metrics: 
1. ```MetricStorage -CW:MetricMonitorUsage```

*  CloudWatch metric API calls:
1. ``` -CW:Requests```
2. ```GetMetricData -CW:GMD-Requests/Metrics```

* CloudWatch alarms:
1. ``` Unknown -CW:AlarmMonitorUsage```
2. ```Unknown -CW:HighResAlarmMonitorUsage```

*  CloudWatch dashboards: 
1. ```DashboardHour DashboardsUsageHour(-Basic)```

*  CloudWatch Logs:
1. ```PutLogEvents -DataProcessing-Bytes```
2. ```PutLogEvents -VendedLog-Bytes```
3. ```HourlyStorageMetering -TimedStorage-ByteHrs```

*  CloudWatch Events: 
1. ```AWSEvents PutEvents -Event(-64K-Chunks)|Request```

Once you understand what you were charged 
Please refer to the Resolution section in the Link : https://aws.amazon.com/premiumsupport/knowledge-center/cloudwatch-understand-and-reduce-charges

How do I reduce "CW:GMD-Metrics" costs?

相關內容