observability-cli-guideslisted

# Observability CLI Guides One reference file per stack, carrying everything the package knows about it: the query CLI and how to set it up, the discovery-then-query commands per signal, how its configuration is displayed and proven, and what its `stack_config` persists. Pick the observed stack's reference, then follow the linked official docs — the fetched page is the source of truth, not memory. The method is the same everywhere: authenticate, **discover** what the service emits, then **query** what you discovered. ## Pick the backend The list of built-in stacks — every value the MCP server's `STACKS` accepts, with its reference, CLI, and aliases — is [references/builtin-stacks.md](references/builtin-stacks.md); it is what `backend-configuration` (its `## Check` and `## Switch`) and `/odd-config` read. The query surface per backend: | Backend | CLI | Reference | | --- | --- | --- | | Local oddyssey stack (`local`) | `gcx` via `setup-local-stack` | [references/local.md](references/local.md), routing to grafana.md | | Grafana (self-hosted, Cloud — `grafana`) | `gcx` | [references/grafana.md](references/grafana.md) | | Datadog | Pup CLI (`pup`) | [references/datadog.md](references/datadog.md) | | Dynatrace | `dtctl` (DQL) | [references/dynatrace.md](references/dynatrace.md) | | Azure Monitor (App Insights, Log Analytics) | `az` (KQL) | [references/azure-monitor.md](references/azure-monitor.md) | | AWS CloudWatch + X-Ray | `aws` | [references/cloudwatch.md](references/cloud