This is really interesting. Some time ago I had a problem, CloudWatch costs increased, and I had to find the root cause. Suddenly we were paying 100 USD per day!
I did reverse engineering and found that one particular LogGroup ingested HUGE amount of data. That was uncommon in our application. Developers checked the microservice associated with that log group, and found out that there was a bug in the code that caused countless unnecessary logs to be sent to CloudWatch.
That whole story gave me an idea to implement CloudWatch Cost Insights functionality in the CloudPouch application. It connects to your AWS account, gets a list of your LogGroups and analyses their metrics to find out which ingested how much data. Everything is presented in the table, so it's easy to spot which LogGroup is responsible for the sudden cost spike. The result looks like that:
This is really interesting. Some time ago I had a problem, CloudWatch costs increased, and I had to find the root cause. Suddenly we were paying 100 USD per day!
I did reverse engineering and found that one particular LogGroup ingested HUGE amount of data. That was uncommon in our application. Developers checked the microservice associated with that log group, and found out that there was a bug in the code that caused countless unnecessary logs to be sent to CloudWatch.
That whole story gave me an idea to implement CloudWatch Cost Insights functionality in the CloudPouch application. It connects to your AWS account, gets a list of your LogGroups and analyses their metrics to find out which ingested how much data. Everything is presented in the table, so it's easy to spot which LogGroup is responsible for the sudden cost spike. The result looks like that:
More about CloudPouch here.