Debug with Grafana

Answer the user's question with the least expensive reliable evidence. No signal is a prerequisite: a known trace or targeted log can be the first check.

Scope and safety

Reuse supplied scope, alert/panel queries, links, IDs, incident times, and known changes. Do not assume an ambiguous reference is an API identifier; resolve it only when needed for the next check. Ask only for information that blocks progress. Preserve per-alert labels; grouped labels may omit affected tenants or operations. Alert firing time is not proven failure onset: account for lookback and pending duration.

Confirm the context and datasource serve the target. Reuse their names/UIDs; pass the same --context <context> on remote commands. Pin fixed UTC bounds for time-based queries and comparisons. Discover only missing routing, schema, or command details needed for the next check; do not equate identity labels across signals without verification.