Instead of capturing traces all of the time which has a CPU, memory and storage overhead that can be quite brutal, we "backtrace" errors. Think of it as following an exception bubbling-up a program execution stack... but through the network. That is then correlated to the services impacted all the way to your public API's.
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? :)
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? :)