Comment by troupo
21 hours ago
> 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.
21 hours ago
> 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).
> Imagine for example looking for http status code 500 in an api log over the past hour.
1. On a blog that no one visits maybe?
2. It's called a grep
3. For bigger projects it's called sentry
Dude, really open your mind and stop arguing mindlessly. We're using this to great success on a serious sass product with hundreds of thousands of users. I'm not some AI influencer, or blowing smoke.
The source of errors can be whatever you like. Sentry, grep, whatever. Its not the point. The point is that many of these errors are real issues, and can be fixed automatically and safely by agentic systems. It really saves time, and work by our team leaving them to actually concentrate on the thing that delivers real value.
[dead]