Observability/diagnostics topics are currently scattered across the Runtime sidebar (runtime/_data.ts):
- Debugging (
/runtime/fundamentals/debugging/) lives under Guides
- OpenTelemetry (
/runtime/fundamentals/open_telemetry/) lives under Advanced, between Cron and Loader hooks
- There is no profiling page at all, even though Deno has profiling-related tooling (V8 inspector/CPU profiles,
--v8-flags, etc.)
These all serve the same user intent — "my program is running, how do I observe/diagnose it?" — and should be grouped into a dedicated sidebar section, e.g. Debugging & observability (or just Observability), containing:
- Debugging
- OpenTelemetry
- Profiling (new page to be written)
- Potentially related material like the
deno coverage/inspector workflows where it makes sense
This would make these features far more discoverable than having them split between a generic Guides list and the Advanced grab-bag.
Observability/diagnostics topics are currently scattered across the Runtime sidebar (
runtime/_data.ts):/runtime/fundamentals/debugging/) lives under Guides/runtime/fundamentals/open_telemetry/) lives under Advanced, between Cron and Loader hooks--v8-flags, etc.)These all serve the same user intent — "my program is running, how do I observe/diagnose it?" — and should be grouped into a dedicated sidebar section, e.g. Debugging & observability (or just Observability), containing:
deno coverage/inspector workflows where it makes senseThis would make these features far more discoverable than having them split between a generic Guides list and the Advanced grab-bag.