Cloudwatch Dashboard - Best practice for use and cost

Question

Good afternoon.  I have a server the sends logs to a log-stream and I wish to have 3 graphs with a count of WARNING, ERROR and CRITICAL.  I did a multi-dimension query, separated and things worked perfect, the issue is after 3 hours it dropped off (then I noticed the query past 3 hour message) so I can't do that.

So looking around I see the widget option to use Logs as a source.  From there I can pick that stream, but the query process looks a bit much, I want to say here is the source, find that string and count those.   Before I take on that task of learning, will I be hit with the same limit?

I want to have an ongoing line graph showing the counts, a cloudwatch alert if a threshold is met, I know they charge for custom metrics AND I can really use this type of logic for others if I can use the logs, query on the fly and keep that count going.

Thanks all.

Accepted Answer

When you build a dashboard, only widgets powered by Metrics Insights queries are limited to the latest 3 hours currently. All other widget sources will allow you to query longer time spans.

Answer

Ah ok ... So that explains why I was getting that 3 hour drop off.   So I am going to play a bit more as I continue this, appreciate the replies as this is a big help.

Answer

Have you considered creating a graph based on a log insights query using the stat?
I dont think you will hit the limit.

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_Insights-Visualizing-Log-Data.html

Cloudwatch Dashboard - Best practice for use and cost

Relevant content