← Back to context

Comment by ManuelKiessling

2 days ago

https://github.com/dx-tooling/platform-problem-monitoring-co... could have a useful approach, too: it finds patterns in log lines and gives you a summary in the sense of „these 500 lines are all technically different, but they are all saying the same“.

the patter matcher is interesting to also collapse log lines and compare that between runs, thank you!

In my tool I was going more of a premise that it's frequently difficult to even say what you're looking for so I wanted to have some step after reading logs to say what should be actually analyzed further which naturally requires to have some model

very interesting, curious if there is any downside to running this at scale (compute?)

  • I'd assume it probably depends how large and varied your logs are?

    But, my guess, I could see an algorithm like that being very fast. It's basically just doing a form of compression, so I'm thinking ballpark, like similar amount to just zipping the log

    Can't be anything CLOSE to the compute cost of running any part of the file through an LLM haha