Ingesting observability data is one thing! Visualizing it in a way that people understand what the data means is another!
I am currently working with a friend on a joint presentation about #serverless observability best practices. But - not just about capturing the data - but - also how to present it best so that SREs that are responsible for such an app/architecture can be more efficient in knowing what to do next!
I was hoping to get some feedback here on whether the dashboard we put together (still work in progress) is easy/hard to understand, contains/misses relevant data.
Thanks a ton in advance
1 Like
Wow that’s a pretty neat idea. I like it a lot! 
After just a couple of seconds I understood most of the dashboard, so I’d say it’s very well made.
It took me a while to understand why only the first step in each column has a success rate → I’d make this full width in the column so that it’s clear without reading the title of the card. Same for the traces.
One more thing: from a user perspective, I would move the dynamic data above the architecture overview. Because if I know the dashboard, I’ll most likely care about this one first.
1 Like
thanks for the great feedback 
1 Like
This looks great, Andi. As Katharina mentioned, the tiles appear a bit small. Since we’re working with Strato’s responsive UI, it can be challenging for users to get a full overview at a glance. That said, the Dashboard itself is very intuitive and easy to understand. From an application owner’s perspective, it would be even more valuable if we could also display the services responsible for each stage. Adding that context would provide the team with deeper insights and make the Dashboard more actionable.
1 Like
