Terminal
Terminal/Skill
Traces Konnect Event Gateway traffic through listeners, hostnames, clusters, auth and policies to find the failing hop.
By Kong
Works with
npx skills add kong/ai-marketplace --skill konnect-event-gatewayTroubleshoot Event Gateway using its own entity model instead of forcing it into standard gateway assumptions.
Default to following the request path end to end: client -> listener -> virtual cluster -> backend cluster -> policy and auth
Own the diagnosis of the failing Event Gateway hop. Hand off implementation or non-Event-Gateway platform problems once that hop is clear.
kong-konnect MCP server first for live Event Gateway
inspection.kongctl-query for read-only resource checks and concise summaries where
the CLI surface is available.kongctl-declarative for kongctl YAML
and terraform-konnect when the required Event Gateway resources are already
managed in HCL.konnect-gateway-triage when the blocker is generic
control-plane, data-plane, or rollout health rather than Event Gateway path
semantics.kong-konnect MCP is not connected, say
so early and continue with CLI or user-provided artifacts.Do not reuse generic gateway triage blindly. Event Gateway deserves a dedicated inspection order because the operator objects differ.
Load only the reference file that matches the active branch:
references/event-path-map.md
references/listener-and-hostname-mapping.md
references/cluster-routing-boundaries.md
references/auth-and-policy-order.md
Clarify:
Keep the path concrete before inspecting objects.
Load references/event-path-map.md when the symptom is still too vague to pick
the right Event Gateway hop.
Verify the required objects exist in the same intended environment:
If these objects do not line up in the same scope, stop there and call out the broken chain.
For connection-oriented symptoms, inspect:
Do not treat a TCP or protocol-level connect as proof that the request is authorized or routed correctly.
Load references/listener-and-hostname-mapping.md when the real question is
whether the listener path itself is the wrong one.
Once the listener is correct, verify that the virtual cluster points at the intended backend cluster and that the backend target is the one the operator expects.
Use this step to separate:
Load references/cluster-routing-boundaries.md when the routing chain from
virtual to backend cluster is the main ambiguity.
If clients can reach the listener but fail afterward, inspect:
This is the default path for "connects but gets denied" reports.
Load references/auth-and-policy-order.md when reachability is proven and the
remaining issue is auth or policy evaluation.
Diagnose one primary operator break:
State the evidence that ruled out the neighboring hops. Avoid reporting multiple equally-weighted guesses.
Before answering, verify that you can state:
kongctl-declarative,
terraform-konnect, konnect-access-scope, or
konnect-gateway-triagekonnect-access-scope when the issue is who can view or administer Event
Gateway resources.konnect-gateway-triage when the real problem is generic Konnect Gateway
health, rollout, or connectivity outside Event Gateway object relationships.kongctl-declarative or terraform-konnect when the operator wants to
encode or apply the Event Gateway fix declaratively. Match the repository's
current toolchain.kongctl-query for exact read-only command selection while inspecting
Event Gateway resources.