2 ms·

Cloudwatch is cheap (even free) for small environments and has very small operational overhead. The cost, however, can easily get out of hand and AWS does not

by pid-1 4y ago

Cloudwatch is cheap (even free) for small environments and has very small operational overhead. The cost, however, can easily get out of hand and AWS does not have per resource billing enabled by default. So it might not be obvious which Log Group is responsible for for which charge. I also think its console is way inferior than something like Grafana for searching and visualisation.

OJFord 4y ago
The console (and its appearance in linked services' 'Logs' tab or similar) is infuriating IMO when your model/what you care about isn't the single instance/invocation that the streams are probably set up as, and you just want all the logs from (all occurrences of, but you're not thinking in those terms) 'thing'. E.g. a Lambda serving API requests, and you just want 'the logs'. Other than searching (for something specific) you can only do it (afaik?) with third-party CLI tools, or (found this as I write) v2 (as in, the separate v2 project/binary/distribution methods, not just being up to date :eyeroll:) of the awscli. Short of rearranging your group/stream naming anyway. Whereas what I really want is just to see all of the logs in the group, with the stream they're from as a filterable property. (And maybe keep the hyper-specific-ness as a new 'publisher' (what unique thing put the event in the stream) property or something?)