Skip to content
Skills Library
DevOps & cloud · Learning & explanation

observability-cli-guides

/observability-cli-guides

The package's knowledge of every observability stack it supports, one reference file per stack - the terminal query surface (how to authenticate and query metrics, traces, logs, and profiles from the CLI), how the stack's configuration is displayed and proven, and what its stack_config persists - plus the list of built-in stacks. Use when observing a run, local or remote, and when backend-configuration's Check or Switch need anything about a stack - Grafana (gcx), Datadog (Pup CLI), Dynatrace (dtctl and DQL), Azure Monitor (az), AWS CloudWatch and X-Ray (aws), and the local stack.

Repository
oddyssey ↗
Licence
MIT
Last repository change
21.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
29
Scripts
20
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 20 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/azure-monitor-context.py, scripts/azure-monitor-discover.py, scripts/azure-monitor-logs.py, scripts/azure-monitor-metrics.py, scripts/azure-monitor-traces.py, scripts/azure_monitor_az.py, scripts/check_stack_reference.py, scripts/cloudwatch-context.py

What it does and when to use it

The package's knowledge of every observability stack it supports, one reference file per stack - the terminal query surface (how to authenticate and query metrics, traces, logs, and profiles from the CLI), how the stack's configuration is displayed and proven, and what its stack_config persists - plus the list of built-in stacks. Use when observing a run, local or remote, and when backend-configuration's Check or Switch need anything about a stack - Grafana (gcx), Datadog (Pup CLI), Dynatrace (dtctl and DQL), Azure Monitor (az), AWS CloudWatch and X-Ray (aws), and the local stack.

Original author description

The package's knowledge of every observability stack it supports, one reference file per stack - the terminal query surface (how to authenticate and query metrics, traces, logs, and profiles from the CLI), how the stack's configuration is displayed and proven, and what its stack_config persists - plus the list of built-in stacks. Use when observing a run, local or remote, and when backend-configuration's Check or Switch need anything about a stack - Grafana (gcx), Datadog (Pup CLI), Dynatrace (dtctl and DQL), Azure Monitor (az), AWS CloudWatch and X-Ray (aws), and the local stack.

How it works

  1. Pick the backend
  2. Rules
Original SKILL.md headings · 57 lines, 432 words
SKILL.md preview
---
name: observability-cli-guides
description: The package's knowledge of every observability stack it supports, one reference file per stack - the terminal query surface (how to authenticate and query metrics, traces, logs, and profiles from the CLI), how the stack's configuration is displayed and proven, and what its stack_config persists - plus the list of built-in stacks. Use when observing a run, local or remote, and when backend-configuration's Check or Switch need anything about a stack - Grafana (gcx), Datadog (Pup CLI), Dynatrace (dtctl and DQL), Azure Monitor (az), AWS CloudWatch and X-Ray (aws), and the local stack.
---

# 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/cloudwatch.md) |

Authoring a reference, or a custom stack's guide: every reference follows
[references/CONTRACT.md](references/CONTRACT.md) — the sections it must
carry, what each answers, and who reads it. A mission never opens it.

For the **local oddyssey stack** (the Grafana case), the `setup-local-stack`
skill carries the ready-made gcx context — isolated config and datasource
UIDs. gcx is the stack's mandatory query CLI.

For Grafana — remote or local — the query commands are the scripts under
`scripts/grafana-*.py`; `grafana.md`'s `## Query by signal` is the one
place that states them, with every flag. For Azure Monitor they are the
scripts under `scripts/azure-monitor-*.py`, stated the same way by
`azure-monitor.md`'s `## Query by signal`; for CloudWatch the scripts
under `scripts/cloudwatch-*.py`, stated by `cloudwatch.md`'s.

## Rules

- Recommendations and commands must come from the reference's linked docs,
  fetched — never from memory; CLIs move fast.
- Credentials come from the environment or the caller (env vars, secret
  stores); never invent, echo, or store them.
- Planning notes are a snapshot (last verified 2026-08); the fetched
  official page always overrides them.
- A reference talks about its own backend only — never a comparison with
  another backend's product (routing to the local stack is not one).
- If the stack's backend is not in the table, say so and fall back to the
  backend's documented REST API over `curl` — the discover-then-query
  method still applies.
Files in this package (29)
  • SKILL.md 4 KB
  • references/CONTRACT.md 9 KB
  • references/azure-monitor.md 45 KB
  • references/builtin-stacks.md 2 KB
  • references/cloudwatch.md 52 KB
  • references/datadog.md 16 KB
  • references/dynatrace.md 16 KB
  • references/grafana.md 43 KB
  • references/local.md 8 KB
  • scripts/azure-monitor-context.py 12 KB
  • scripts/azure-monitor-discover.py 12 KB
  • scripts/azure-monitor-logs.py 14 KB
  • scripts/azure-monitor-metrics.py 21 KB
  • scripts/azure-monitor-traces.py 43 KB
  • scripts/azure_monitor_az.py 16 KB
  • scripts/check_stack_reference.py 20 KB
  • scripts/cloudwatch-context.py 15 KB
  • scripts/cloudwatch-discover.py 17 KB
  • scripts/cloudwatch-logs.py 13 KB
  • scripts/cloudwatch-metrics.py 26 KB
  • scripts/cloudwatch-traces.py 48 KB
  • scripts/cloudwatch_aws.py 23 KB
  • scripts/grafana-context.py 11 KB
  • scripts/grafana-discover.py 8 KB
  • scripts/grafana-logs.py 7 KB
  • scripts/grafana-metrics.py 16 KB
  • scripts/grafana-profiles.py 8 KB
  • scripts/grafana-traces.py 62 KB
  • scripts/grafana_gcx.py 21 KB

Versions

The database has no other skills named observability-cli-guides.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version b4ddbe5e85d8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95setup-local-stack
    Configure gcx against the local oddyssey Grafana stack and query its four signals (metrics, traces, logs, profiles) without touching the user's own gcx contexts. Owns the global configuration's "local" stack value. Use when the configured stack is "local", when querying the…
  • 100dtctl
    Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems,…
  • 95backend-configuration
    Own the configured observability backend, in two sections invoked by name. Check: display the configured stack and the instance the runs will hit, prove the CLI connected, guide the user when it is not, and hand the preflight over to the mission. Switch: verify the target…
  • 84use-datadog
    Use the Datadog CLI (pup) for observability tasks. TRIGGER when the user mentions Datadog, monitors, alerts, logs, metrics, APM, traces, incidents, SLOs, dashboards, or any Datadog-related observability work. This skill ensures the agent uses pup instead of raw API calls or the Datadog web UI.
  • 100observability
    Design and implement AWS observability solutions. Use when configuring CloudWatch metrics, logs, alarms, dashboards, Logs Insights queries, X-Ray tracing, anomaly detection, or debugging monitoring gaps.
  • 100datadog
    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.