Loading...
Loading...
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.
npx skill4agent add mulesoft/mulesoft-dx omni-gateway-logs[component][level] message[flex-gateway-agent][info] Running Envoy XDS Service...
[flex-gateway-agent][error] Error authorizing https://anypoint.mulesoft.com: Post "https://anypoint.mulesoft.com/accounts/oauth2/token": dial tcp 54.173.213.129:443: connect: connection timed out
[flex-gateway-envoy][info] all dependencies initialized. starting workers
[flex-external-processor][info] Ext Proc Server successfully started.
[flex-gateway-agent][warn] Registration is using v1 version, but some metrics are only supported for v2. Please renew your registration to avoid errors.<ISO-timestamp> LEVEL [pod-name] component - message2026-02-26T22:56:56.935Z INFO [pbtest1-766cbd68f9-g2r7n] flex-gateway-agent - Running Envoy XDS Service...
2026-02-26T23:01:13.53Z ERROR [pbtest1-766cbd68f9-g2r7n] flex-gateway-agent - Error authorizing https://stgx.anypoint.mulesoft.com: Post "https://anypoint.mulesoft.com/accounts/oauth2/token": dial tcp 54.173.213.129:443: connect: connection timed out
2026-02-26T22:56:57.447Z INFO [pbtest1-766cbd68f9-g2r7n] flex-gateway-agent - Creating gateway| Component | What it does |
|---|---|
| Main agent: gateway lifecycle, registration with Anypoint, config management, token refresh, control-plane sync |
| Envoy proxy: HTTP/HTTPS/gRPC routing, TLS termination, upstream connections, xDS config consumer |
| Fluent Bit: log collection and forwarding |
| External processor (Java): handles external-processing policies |
| OpenTelemetry collector: metrics and tracing export |
Running Envoy XDS Service...
RTMDataSource: Starting
KubernetesDataSource: Starting ← Kubernetes only
Creating gateway
Processing commands
Validating gateway
Generating config
Gateway: Platform=... Mode=connected ReplicaName=...
Writing envoy bootstrap configuration to /var/tmp/mulesoft/flex-gateway/envoy.json
RTMDataSource: Change configuration
flex-gateway-envoy: Starting
flex-gateway-fluent: Starting
flex-external-processor: Starting
all dependencies initialized. starting workers ← from flex-gateway-envoy
Anypoint websocket: connected ← connected mode only
open delta watch ID:1 for ...Cluster... ← xDS subscriptions active
open delta watch ID:2 for ...Listener...all dependencies initialized. starting workers# View last 200 log lines
sudo journalctl -u flex-gateway -n 200 --no-pager
# Stream logs in real-time
sudo journalctl -u flex-gateway -f
# View logs within a time window
sudo journalctl -u flex-gateway --since "2026-06-08 14:00:00" --until "2026-06-08 15:00:00"# View last 200 log lines
docker logs --tail=200 flex-gateway
# Stream logs in real-time
docker logs -f flex-gateway
# View logs with timestamps
docker logs --timestamps flex-gateway<namespace><pod-name># Find gateway pods
kubectl get pods -n <namespace> -l app.kubernetes.io/name=flex-gateway
# View logs from a specific pod
kubectl logs -n <namespace> <pod-name> --tail=200
# View logs from all gateway pods
kubectl logs -n <namespace> -l app.kubernetes.io/name=flex-gateway --all-containers=true --tail=100
# View logs from a previous (crashed) pod instance
kubectl logs -n <namespace> <pod-name> --previous
# Stream logs in real-time
kubectl logs -n <namespace> <pod-name> -f/usr/local/share/mulesoft/flex-gateway/conf.d/logging.yamlapiVersion: gateway.mulesoft.com/v1alpha1
kind: Configuration
metadata:
name: logging
spec:
logging:
runtimeLogs:
logLevel: debuglogLevelinfoflexctl][error]][warn]][info]][debug]ERRORWARNINFODEBUGerrorwarnerror**flex-gateway-agent**flex-gateway-envoy**flex-external-processor**flex-gateway-fluent**open-telemetry-collectorflex-gateway-agentError authorizing https://anypoint.mulesoft.com: ... connection timed out| Log pattern | Severity | Likely cause | Next step |
|---|---|---|---|
| ERROR | Gateway cannot reach Anypoint OAuth endpoint to refresh its token | Check network/firewall rules: the gateway must be able to reach |
| ERROR | Sustained failure to refresh the Anypoint OAuth token; gateway is now disconnected from the control plane | Immediate: restore connectivity to |
| ERROR | A Kubernetes | Remove the |
| WARN | Registration was created with an older version of | Re-register the gateway using the current |
| WARN | Cannot report startup metrics to Anypoint (non-critical: gateway traffic is unaffected) | Check Anypoint connectivity; analytics events will be missing for this startup |
| WARN | Cannot report periodic metrics to Anypoint (non-critical: gateway traffic is unaffected) | Check Anypoint connectivity; analytics data will have gaps |
| ERROR (Envoy access log) | Upstream service not reachable or closed connection | Verify the |
| ERROR | TLS misconfiguration, expired certificate, or incomplete certificate chain | Check certificate validity and expiration; review TLS config in conf.d |
| WARNING (Envoy) | Envoy using a deprecated internal config field | Expected and harmless — known issue in current Omni Gateway versions; ignore unless other problems are present |
| INFO | Normal Anypoint OAuth token refresh cycle | Expected and normal — gateway is proactively refreshing its token; not an error |
## Log Analysis Summary
Period: <start timestamp> – <end timestamp> (or "unknown" if timestamps absent)
Total lines analyzed: <N>
Log level: <INFO / DEBUG / TRACE / mixed>
Platform: <Docker / Kubernetes / Linux>
Mode: <connected / local / unknown>
### Severity Counts
- ERROR: N
- WARN: N
- INFO: N
- DEBUG/TRACE: N
### Component Breakdown
- `flex-gateway-agent`: N lines, X errors
- `flex-gateway-envoy`: N lines, X errors
- `flex-external-processor`: N lines, X errors
- `flex-gateway-fluent`: N lines, X errors
- `open-telemetry-collector`: N lines, X errors
### Top Issues (deduplicated)
1. [Nx flex-gateway-agent] Error authorizing ... connection timed out — hypothesis
2. [Nx flex-gateway-agent] Processing commands errors: Ingress ... — hypothesis
3. ...
### Startup Completion
Gateway reached "all dependencies initialized" / "Anypoint websocket: connected": YES / NO / UNKNOWN
### Root Cause Hypothesis
<One or two sentences on the likely root cause based on patterns and timeline.>
### Recommended Next Steps
1. <Specific action, e.g., "Check egress firewall rules: gateway needs port 443 access to anypoint.mulesoft.com">
2. <Specific action, e.g., "Run `omni-gateway-config` — error suggests an Ingress resource is present">
3. <Specific action, e.g., "Re-register the gateway with current flexctl to upgrade from v1 registration">**omni-gateway-diagnose****omni-gateway-config****omni-gateway-install**