3 ms·
> Dropping valuable observability data to save space is usually shortsighted That's a bit of a blanket statement, too :) I've seen many systems where a lot of
by ofrzeta 1y ago
> Dropping valuable observability data to save space is usually shortsighted
That's a bit of a blanket statement, too :) I've seen many systems where a lot of stuff is logged without much thought. "Connection to database successful" - does this need to be logged on every connection request? Log level info, warning, debug? Codebases are full of this.
- nijave 1y agoYes, it allows you to bisect a program to see the block of code between log statements where the program malfunctioned. More log statements slice the code into smaller blocks meaning less places to look.
- vidro3 1y agoin our app each user polls for a resource availability every 5 mins. do we really need "connection successful" 500x per minute? i dont see this as breaking up the logs into smaller sections. i see it as noise. i'd much rather have a ton of "connection failed" whenever that occurs than the "success" constantly
- throwaway0665 1y agoThere's always another log that could have been key to getting to the bottom of an incident. It's impossible to know completely what will be useful in advance.
- citrin_ru 1y agoProbably not very useful for prod (non debug) logging, but it’s useful when such events are tracked in metrics (success/failure, connect/response times). And modern databases (including ClickHouse) can compress metrics efficiently so not much space will be spent on a few metrics.