Run any Skill in Manus with one click

omni-gateway-diagnose

Stars9

Forks20

UpdatedJuly 17, 2026 at 13:44

Diagnose Omni Gateway errors and failures given any combination of log output, dump files, or symptom descriptions. Use when the user reports a gateway error (5xx, 4xx, gateway unreachable, policy not applying), has log output to analyze, needs to decide whether to request debug logs from a customer, or needs to determine whether an issue requires escalation to the gateway team.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mulesoft

mulesoft/mulesoft-dx

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	omni-gateway-diagnose
description	Diagnose Omni Gateway errors and failures given any combination of log output, dump files, or symptom descriptions. Use when the user reports a gateway error (5xx, 4xx, gateway unreachable, policy not applying), has log output to analyze, needs to decide whether to request debug logs from a customer, or needs to determine whether an issue requires escalation to the gateway team.

Diagnose Gateway Error

Triage by Symptom

Symptom	First Check	Invoke Skill
5xx errors on all requests	Upstream connectivity, spec.address binding	`omni-gateway-config`
4xx errors (auth/policy)	PolicyBinding targeting, policy config	`omni-gateway-config`
Gateway unreachable / port not responding	Listen address (0.0.0.0 vs localhost), port conflicts	`omni-gateway-config`
Policy not applying	PolicyBinding → ApiInstance cross-reference	`omni-gateway-config`
`upstream connect error` / connection refused	Upstream service health, routes config	`omni-gateway-logs`
TLS handshake failures	Certificate validity, TLS config in conf.d	`omni-gateway-logs`
`xDS disconnected` / control plane errors	Anypoint connectivity, registration token validity	`omni-gateway-logs`
STARTED state never reached	Registration artifact, conf.d correctness	`omni-gateway-install` (re-register), then `omni-gateway-config`
Known-good config still failing	Live deployed state may differ from conf.d	`omni-gateway-dump`

By Available Artifact

Logs provided → invoke omni-gateway-logs
conf.d directory available → invoke omni-gateway-config
Dump file provided → invoke omni-gateway-dump
Symptom description only → ask the user which artifacts are available before proceeding

Escalation Decision

Self-serviceable

These issues can be resolved without escalating to the gateway team:

Misconfigured PolicyBinding (wrong targetRef, missing ApiInstance)
Wrong spec.address (using localhost instead of 0.0.0.0)
Upstream service unreachable (network/firewall issue outside the gateway)
Expired or revoked Anypoint registration token

Escalate to Gateway Team

These issues require gateway team involvement:

Repeated xDS sync failure after verifying a valid configuration
Envoy process crash (crash loop, OOMKill)
STARTED state never reached after valid registration and correct conf.d
Issue is reproducible after configuration is confirmed valid by omni-gateway-config

Escalation Package Checklist

Collect all of the following before opening a support ticket:

Full gateway logs at debug level (see omni-gateway-logs for how to enable)
Diagnostic dump file (see omni-gateway-dump for analysis before escalating)
conf.d/ listing with secrets omitted (file names + kind/name inventory only)
flexctl version output
Platform: Linux / Docker / Kubernetes / CloudHub
Reproducible steps or a timeline of when the failure started

Related Jobs

omni-gateway-logs — parse log output to surface errors and anomalies
omni-gateway-config — structural and cross-reference validation of conf.d files
omni-gateway-dump — interpret a diagnostic dump ZIP for live gateway state

More from this repository

same repository

omni-gateway-benchmark

mulesoft/mulesoft-dx

Execute performance and load benchmarks against MuleSoft Omni Gateway (formerly Flex Gateway) on Amazon EKS using the harness under this skill's `scripts/` directory. Use when the user wants to provision the benchmark cluster, deploy a specific Flex version, drive load with k6, capture Grafana evidence, retrieve a Markdown report and dashboard PNGs, compare gateway versions, validate rate-limit or client-id-enforcement behavior under load, or tear the environment back down. Covers the full lifecycle: AWS provisioning, image push, deploy, run, report, and teardown.

2026-07-179

omni-gateway-config

mulesoft/mulesoft-dx

Read and validate YAML configuration files in an Omni Gateway conf.d directory. Use when a gateway returns unexpected 4xx/5xx errors after a config change and the user suspects a misconfiguration; when a new PolicyBinding or ApiInstance was added and is silently not taking effect; when conf.d files were edited manually and the user wants to catch errors before restarting the gateway; or when omni-gateway-diagnose determines that conf.d is the likely root cause.

2026-07-179

omni-gateway-dump

mulesoft/mulesoft-dx

Interpret the contents of an Omni Gateway diagnostic dump ZIP file to identify the live state of API instances, service bindings, policy configuration, and known anomalies. Use when the user has a gateway dump file and wants to understand what was deployed at the time of capture, find orphaned or missing resources, compare live state against the conf.d configuration, or diagnose a gateway failure using a support-submitted dump.

2026-07-179

omni-gateway-install

mulesoft/mulesoft-dx

Install and register MuleSoft Omni Gateway on self-managed infrastructure: Linux (Ubuntu/Debian via APT), Docker or Docker Compose, or Kubernetes / OpenShift (Helm). Use when the user wants to install Omni Gateway, connect it to Anypoint Platform's control plane, re-register after a token expires or a new environment is needed, and verify the gateway is running. CloudHub 2.0 managed deployments are not covered by this skill bundle.

2026-07-179

omni-gateway-logs

mulesoft/mulesoft-dx

Parse and interpret Omni Gateway log output to surface errors, warnings, and anomalies. Use when the user shares gateway logs and wants to understand what went wrong, identify upstream connectivity failures, find TLS or authentication errors, diagnose policy evaluation problems, or get a structured summary of log activity with recommended next steps.

2026-07-179

review-pr

mulesoft/mulesoft-dx

Use this skill when asked to "review a PR", "review pull request", "analyse PR", or "check PR" in the mulesoft-dx repo. Guides the full review process: checkout, categorize changed files, run deterministic validators, perform AI analysis, and produce a structured verdict.

2026-07-179

name	omni-gateway-diagnose
description	Diagnose Omni Gateway errors and failures given any combination of log output, dump files, or symptom descriptions. Use when the user reports a gateway error (5xx, 4xx, gateway unreachable, policy not applying), has log output to analyze, needs to decide whether to request debug logs from a customer, or needs to determine whether an issue requires escalation to the gateway team.

Diagnose Gateway Error

Triage by Symptom

Symptom	First Check	Invoke Skill
5xx errors on all requests	Upstream connectivity, spec.address binding	`omni-gateway-config`
4xx errors (auth/policy)	PolicyBinding targeting, policy config	`omni-gateway-config`
Gateway unreachable / port not responding	Listen address (0.0.0.0 vs localhost), port conflicts	`omni-gateway-config`
Policy not applying	PolicyBinding → ApiInstance cross-reference	`omni-gateway-config`
`upstream connect error` / connection refused	Upstream service health, routes config	`omni-gateway-logs`
TLS handshake failures	Certificate validity, TLS config in conf.d	`omni-gateway-logs`
`xDS disconnected` / control plane errors	Anypoint connectivity, registration token validity	`omni-gateway-logs`
STARTED state never reached	Registration artifact, conf.d correctness	`omni-gateway-install` (re-register), then `omni-gateway-config`
Known-good config still failing	Live deployed state may differ from conf.d	`omni-gateway-dump`

By Available Artifact

Logs provided → invoke omni-gateway-logs
conf.d directory available → invoke omni-gateway-config
Dump file provided → invoke omni-gateway-dump
Symptom description only → ask the user which artifacts are available before proceeding

Escalation Decision

Self-serviceable

These issues can be resolved without escalating to the gateway team:

Misconfigured PolicyBinding (wrong targetRef, missing ApiInstance)
Wrong spec.address (using localhost instead of 0.0.0.0)
Upstream service unreachable (network/firewall issue outside the gateway)
Expired or revoked Anypoint registration token

Escalate to Gateway Team

These issues require gateway team involvement:

Repeated xDS sync failure after verifying a valid configuration
Envoy process crash (crash loop, OOMKill)
STARTED state never reached after valid registration and correct conf.d
Issue is reproducible after configuration is confirmed valid by omni-gateway-config

Escalation Package Checklist

Collect all of the following before opening a support ticket:

Full gateway logs at debug level (see omni-gateway-logs for how to enable)
Diagnostic dump file (see omni-gateway-dump for analysis before escalating)
conf.d/ listing with secrets omitted (file names + kind/name inventory only)
flexctl version output
Platform: Linux / Docker / Kubernetes / CloudHub
Reproducible steps or a timeline of when the failure started

Related Jobs

omni-gateway-logs — parse log output to surface errors and anomalies
omni-gateway-config — structural and cross-reference validation of conf.d files
omni-gateway-dump — interpret a diagnostic dump ZIP for live gateway state