If I understood correctly, for that particular month, there were 1900.294 metrics in total. With the first 1800 you crossed 10000 since you started using Cloudwatch. Those 1800 were charged @ $0.3. The remaining 100.294 are charged @ $0.1 since you crossed 10000. This is the only possible explanation in my view.
Hi, do you use both custom metrics and detailed monitoring? Is the count above only one of the 2 or the sum of both?
FYI, both detailed monitoring and custom metrics count towards tiers - therefore if you look at only one of the 2, you might get the impression that you have less than 10,000 metrics in the first tier, but that could be e.g. 1,800 custom metrics and 8,200 detailed monitoring metrics in it for example.
Can you please share more details on what filters got you those numbers?
Doubt about cloudwatch metricsasked 5 months ago
Why the LoginFailures metric showing no data for RDS MySQL instance?asked 4 years ago
How can I optimize costs associated with publishing Lambda custom metrics to CloudWatch?Accepted Answerasked 2 years ago
want to activate Disk Usage and Ram Usage metricsAccepted Answerasked 8 months ago
Help me understandasked 2 months ago
CloudWatch how to disable metrics?asked 4 years ago
HTTP API metrics not showing in CloudWatch automatic dashboardasked 8 months ago
AWS Cloudwatch - usage questionsasked 4 months ago
IP Metrics for SES dedicated IPs from Microsoft SNDS are missing in CloudWatchasked 7 months ago
How the Detailed monitoring is actually charged.asked a year ago