> backtrace errors on demand to understand end-user impact and prioritise what to work on
So you can work out what the issues on my deployment are, and then prioritize them? How does that work?
So you can work out what the issues on my deployment are, and then prioritize them? How does that work?
We are working on the PoC's for async processes too! (queues, pubsubs, fanouts, streams); and session/user-level impact metrics, coming out real soon! :)
By the way... this will also be used to build better context in our discovery / knowledge application, because.... well... why wait until something goes wrong to understand the impact of what you are doing? :)