Traditionally, a berserkr is a bear-shirt ber (bear) + serkr (shirt), letting you harness the power of the bear. That's the shirt we want you reaching for when the pager goes off at 3am. The Berserk observability engine works the way those warriors fought: by brute-force, and it invites you to go berserk: throw all the logs, traces, and metrics you want at it and tear straight through. It plays well with your existing AI solutions too. We're ready to take on early customers who want to be part of the journey. https://lnkd.in/eBgF8jP3
Thomas Anagrius
12h
Super proud of what we have achieved already. A real hyper-sonic, flexible beast of an event search engine. Vector search on log patterns, fast mini-graphs for traces allowing you to work with whole traces and do aggregations and filtering... So much fun.
So it begins...
Love it , this is so true “Internal server error" usually lives in a log line; the entry-point service lives on a span; the only thing tying them together is the trace they share. In most platforms that's two stores, two query languages, and a hand-rolled join” - CC Ganesh Sahu