AWS Cost Saving Recommendations

Re:AWS Cost Saving Recommendations by hughrr on Wednesday July 14, 2021 @03:22AM (#27830545)

The only thing I can actually suggest is to avoid the hell out of logging if you can. It’s a really expensive concern and should be treated so from day one. If your system has nothing actionable to log them don’t log it.

At a high level from observations of trying to handle 100Gb a day.

Cloudwatch is inflexible and expensive.

ELK is expensive to run and administer. The commercial variants are even worse.

Splunk is expensive and slow.

Datadog is expensive.

Loki is expensive to run and administer.

ryslogd and grep starts to feel like a viable solution eventually. Then you realise that you need about 50MB of that 100G a day of logs and enlightenment comes.

[ Parent | on HN ]

Re:AWS Cost Saving Recommendations by blandflakes on Wednesday July 14, 2021 @09:41AM (#27832881)

Thanks for the response, yeah that resonates. I think the sheer volume of logs has been what necessitates expensive solutions.

I've found that my current team really relies on those and an event store for observability, and it's just clunky and awful. Logging for, well, logging purposes instead would be a dramatic improvement.

[ Parent | on HN ]