> scanning logs for errors
famously a good job for a tool that takes 10-50k logs to run out of context and forget what it's doing.
> scanning logs for errors
famously a good job for a tool that takes 10-50k logs to run out of context and forget what it's doing.
Not really? Imagine for example looking for http status code 500 in an api log over the past hour. The nice thing here is it doesn’t matter if you get them all because it’s reoccur (or not).
[dead]