https://www.statuspage.io/ or an open equivalent (https://github.com/oneuptime/oneuptime) perhaps? It's a straightforward implementation shim to distill from engineering telemetry to the non tech interface in my experience. Think of this as scaling engineering comms to non engineering parts of the org.
yeah but in my experience it's either the information is very shallow (like status page) or too technical (like traces). i feel like non engineering parts of the org still want to have a view of what's slow, what's fast, how much data we ingested and things like that