Terminal
Terminal/Skill
Finds why Konnect analytics, Explorer, or Debugger data is missing, delayed, or narrower than expected, by checking scope and dataset.
By Kong
Works with
npx skills add kong/ai-marketplace --skill konnect-observability-triageExplain why Konnect observability data is missing, partial, delayed, or scoped unexpectedly, and direct the operator to the right dataset and next action.
Default to proving traffic and scope before concluding that observability is broken. This skill owns observability diagnosis, not generic gateway connectivity, portal publication, or operator-access troubleshooting.
kong-konnect MCP server for live inspection of the relevant
Konnect surface when available.kongctl-query for read-only checks on organizations, control planes,
APIs, and adjacent resources that determine where telemetry should appear.konnect-access-scope when the problem is primarily who can see the
data.konnect-gateway-triage when the real issue is no traffic or unhealthy
gateway connectivity.kong-konnect MCP is not connected, say
so early and continue with CLI or user-provided artifacts.Load only the reference file that matches the active branch:
references/dataset-map.md
references/scope-time-window-checks.md
references/visibility-vs-ingestion.md
Clarify what the user expects to see:
Do not assume these are interchangeable. Missing data often starts with the wrong surface selection or the wrong granularity of evidence.
Load references/dataset-map.md when the operator is mixing API, LLM, and
platform observability surfaces.
Confirm:
Many empty dashboards are valid results for the chosen scope or time window.
Load references/scope-time-window-checks.md when the likely problem is the
slice being inspected rather than the telemetry itself.
Before diagnosing telemetry ingestion, verify that the thing being observed is actually receiving traffic or events.
konnect-gateway-triage.konnect-api-catalog or konnect-api-publish
instead of staying in observability.Use the simplest mapping that fits the symptom:
If the user is looking in the wrong dataset, say so explicitly instead of calling it missing data.
Investigate whether missing data is caused by:
Keep "configuration missing" separate from "viewer cannot see it." Prefer the narrowest explanation that matches the evidence. Do not jump from one empty view to a global ingestion claim.
Load references/visibility-vs-ingestion.md when the hard question is whether
the data is absent, delayed, hidden, or only partially scoped.
Classify the issue as:
Before answering, verify that you can state:
konnect-gateway-triage when the root problem is absent or unhealthy
runtime traffic.konnect-access-scope when the data likely exists but the caller cannot
see it.konnect-api-catalog or konnect-api-publish when the real issue is
object readiness or publication state rather than telemetry.kongctl-query for exact resource inspection commands that support the
diagnosis.