OpenTelemetry Expands Hybrid Enterprise Reach via Mainframe SIG Instrumentation Effort

The Open Mainframe Project, in ongoing collaboration with the Cloud Native Computing Foundation (CNCF) and the OpenTelemetry project, has advanced its Special Interest Group (SIG) OpenTelemetry on Mainframe roadmap to accelerate open telemetry standards across enterprise hybrid infrastructure. The initiative is actively driving three technical focus areas: establishing unified OpenTelemetry Semantic Conventions tailored to mainframe architectures, engineering native code instrumentation and SDK support for languages including COBOL, PL/1, Assembler, and REXX, and compiling native OpenTelemetry Collector distributions for z/OS and Linux on IBM Z (s390x). For site reliability engineers, platform architects, and enterprise operations teams, this development addresses one of the most stubborn blind spots in modern distributed tracing. While cloud-native services running on Kubernetes and managed cloud platforms have largely standardized on OpenTelemetry for metrics, logs, and traces, transactional backends on mainframes have remained isolated within proprietary monitoring silos. When an end-user request spans from a modern mobile gateway down to a core banking or supply-chain mainframe transaction, context propagation typically halts, forcing teams to correlate disparate proprietary logs manually during outages. Establishing vendor-neutral instrumentation across legacy systems eliminates this observability boundary. This push reflects a wider maturation across the cloud-native ecosystem as OpenTelemetry cements its position alongside Kubernetes and Prometheus as core infrastructure plumbing. Having achieved graduated status in the CNCF, the OpenTelemetry standard is expanding beyond greenfield container environments into legacy mission-critical computing. Rather than requiring enterprises to rewrite legacy applications or depend on expensive third-party APM translation agents, standardizing OTLP ingest and context propagation natively at the mainframe level unifies enterprise observability under a single query model. In practice, platform teams operating hybrid environments should evaluate their current telemetry pipelines and assess where transaction boundaries fail. Engineering organizations should prepare for incoming mainframe semantic conventions by auditing how transaction IDs and distributed context (W3C Trace Context headers) pass across message queues, MQ channels, and REST gateways interfacing with backend systems. While native mainframe SDKs progress through active testing, teams can begin running OpenTelemetry Collector instances on Linux on IBM Z to normalize and route existing platform metrics directly into standard OTLP-compliant observability storage, cutting down agent complexity and operational overhead.