Flex Gateway connected mode — Runtime Manager DEBUG logs appear on one gateway but not another with identical configuration

SYMPTOM

On self-managed Flex/Omni Gateways in connected mode, a runtime log level (e.g. DEBUG) enabled from Runtime Manager → Gateway → Runtime Configuration streams logs for one gateway but not for another gateway that appears identically configured. The gateways compare identical side by side, and the difference is consistent across restarts and environments.

CAUSE

Two configuration sources on the gateway set the Anypoint log output and conflict: the platform-managed configuration pushed by Anypoint at registration (log streaming enabled) and a local declarative logging configuration file applied on the gateway (log streaming disabled). Flex Gateway merges overlapping declarative resources in a deterministic order; when two sources set the same option, the one processed last takes effect. Because the platform-managed configuration is named uniquely per gateway while the local file has the same name on every gateway, the merge order can differ between two gateways — so the same conflicting pair produces opposite results (enabled on one gateway, disabled on another).

SOLUTION

Let the Anypoint platform own the logging output for connected-mode gateways and remove the conflicting local setting on every gateway:

1. On each gateway, locate the local declarative configuration file that sets the logging output — a Configuration resource named logging-config whose spec.logging sets accessLogs and/or runtimeLogs outputs anypoint to disabled.
2. Remove that file, or remove the outputs.anypoint: disabled entries from it, so the local file no longer disables the Anypoint log output.
3. Apply this change on all gateways in the pair — not only the one that is broken. A gateway that currently works does so only by coincidence of merge order and can regress after a future re-registration.
4. Re-apply the configuration and restart the gateway pods.
5. Confirm in Runtime Manager that runtime and access logs now stream for every gateway.

If local declarative configuration files are required for other purposes, ensure they do not include the logging output section for connected-mode gateways.

References

Flex Gateway configuration and logging: check docs.mulesoft.com (Flex Gateway → Configure Logging / Third-party log configuration).