Oracle WebLogic Server powers countless enterprise Java systems. But getting observability out of it has always meant juggling multiple tools, agents, and dashboards with no way to correlate signals across applications and infrastructure.

I recently worked on standardizing observability across heterogeneous enterprise architectures at Banco do Brasil — from mainframe COBOL to cloud-native systems to on-premises WebLogic. The goal was simple: one semantic convention, one backend, one view of an entire transaction.

This post walks through building a custom, minimal OpenTelemetry Collector for WebLogic that makes this possible.

Repository: github.com/vinnicius/weblogic-opentelemetry

What We're Building

Application (OTel Java Agent) ──┐ Host (CPU/memory/disk) ──┼──→ otelcol-weblogic ──→ Your Backend WebLogic logs (domain files) ──┤ (OTLP only) (Tempo, Loki, JVM metrics (via JMX) ──┘ Jaeger, etc.)

Enter fullscreen mode

Exit fullscreen mode

A single container that ingests four signal types and exports…