When you’re running APIs and agentic assets at scale, visibility isn’t optional. It’s the difference between catching a problem in seconds and spending hours chasing symptoms. Until now, getting telemetry out of Managed Omni Gateway meant routing it through Anypoint Platform via the OpenTelemetry exporter.
For many teams that’s a workable default, but enterprises need more control over where their data travels. For organizations with data residency requirements, routing telemetry through the control plane isn’t just inconvenient, it’s prohibited. Managed Omni Gateway now exports telemetry directly from the runtime, so your observability data never has to touch the control plane at all. If your team lives in New Relic, Splunk, Datadog, or any OpenTelemetry-compliant collector, gateway telemetry can flow there alongside everything else you already monitor.
Two Signals, Independently Routable
Managed Omni Gateway exports two types of telemetry — logs and traces — and you control where each one goes.
Logs
Runtime logs cover gateway operations: startup, shutdown, deployed assets, policies, and configuration errors.
Access logs cover request and response data for the specific asset instances you choose to instrument — opt-in.
Traces
Tracing tracks requests as they move through the gateway and once those traces land in your OpenTelemetry collector, they join the broader picture. You can correlate gateway behavior with traces from your application layer, infrastructure, and downstream services — a single connected view across your entire stack.
Demo
Ready to set it up? The release notes walk through the full configuration for both signals:
