What problem does it solve? Setting up the gcx CLI against the local oddyssey observability stack by hand means reconstructing ports, contexts, and datasource UIDs from prose, risking clobbering the user's own gcx contexts. This Skill automates that configuration in an isolated context and inventories which services actually emit metrics, traces, logs, and profiles before any observation begins. ## Core Features & Use Cases - Isolated gcx context setup: Reads host ports from the global configuration, writes an isolated gcx context at a stable path, and verifies connectivity with gcx config check, leaving the user's own contexts untouched. - One-call service inventory: Probes multiple services concurrently across all four signals (Tempo traces, Prometheus metrics, Loki logs, Pyroscope profiles), reporting identity, operations, metric names, and counter baselines, with absence reported as loudly as presence. - Container configuration reference: Documents the full otel-lgtm environment variable surface (retention, OTLP forwarding, OBI, Grafana settings) aligned to the pinned image tag. - Use Case: Before observing a service on the local stack, run the setup script to get a working gcx context, then probe the service to learn which signals it carries and capture counter baselines that later queries subtract from. ## Quick Start Ask the agent to configure gcx against the local oddyssey stack and probe your service's signals using this skill's scripts.
