Create an 'Instrumentation Joyride'

[austinlparker]

Feature Request

Currently, the frontend/webstore component doesn't really give people much information about what's actually happening in terms of backend instrumentation. Errors and latency that are induced by failure scenarios simply occur, without much to indicate what's happening or why. To improve the interactivity of the demo environment, and to help draw connections between user interactions and backend services/instrumentation, we should create some sort of joyride (aka, guided tour) to educate users about available dashboards, queries, alerts, etc. being generated by the demo.

Open Questions

• How would this interact with BYOC/non-bundled observability backends? We can obviously link into Grafana dashboards we create, but we would also need the ability to swap out those links for forks.
• This seems like a pretty big lift, is it worth pursuing?

[julianocosta89]

Oh, this is nice! Not sure about the amount of effort we would need in here, but I totally agree that we need to improve the scenarios we have in the demo.

When enabling the FF I would expect getting errors, crashes and long response times in the frontend.