Improve observability settings page
Context
To configure Error Tracking, users have to go to "Project > Settings > Monitor > Error Tracking" to:
- enable Error Tracking
- then edit some other settings in that page:
But to configure Logs/Traces/Metrics, users have to:
- enable the feature directly in the page (shown here)
- Edit their application source to add instrumentation code and/or install the opentelemetry collector as described in the logs/metrics/traces documentation pages.
There is not settings visible in the Project > Settings > Monitor page - no section for logs/traces/metrics.
Problem
We got 3 user feedback in the last few weeks saying that this is confusing.
They were expecting to see something in project settings to help them configure log/trace/metrics:
- "I hope I'm not just being dense, but I can't find any reference to logs or metrics under Monitor or Settings > Monitor" (zendesk ticket)
- "I thought [...] there was a "monitor -> tracing" option under "settings" that you had to enable. It's a bit of a strange UX, I would expect an "enable" option might be found under settings. It sounds like a setting." (slack thread)
- I don't see Monitor => Tracing in settings for this sample repo: do I need to enable a feature flag on a per-repo basis? (slack thread)
Design question
What can we do to solve this issue?
Some ideas:
- add log/trace/metrics (or "observability?) sections in settings > monitor with some documentation (and link to detailed doc page) on how to configure the features
- replace the current "enable observability" onboarding screen by a toggle in settings > monitor
This is related to #2505 and could be tackled together to improve the overall onboarding workflow.
Edited by Sacha Guyon