Contact us
A clear read on what OpenTelemetry actually does on the mainframe and a framework to decide if you need it now, later, or not at all.
There is a lot of talk in the mainframe world about OpenTelemetry (OTel). While it is easy to read about it, few can answer the core question of what problem it is trying to solve for them. OpenTelemetry is an open standard for the transport of operational data about applications (opentelemetry.io) that is maintained by the Cloud Native Computing Foundation. This ebook attempts to describe what OpenTelemetry does, why the mainframe is a special case, and how one can read the blurb from your vendor. We will then develop a simple framework that can be used to make a decision about OpenTelemetry with your team. Note that this is written for people who run mainframes and not for people who sell pipelines. We consider “not yet” to be a valid answer.
Trust bullets
✓ Independent — no product tour, no competitor named, no pitch
✓ Written for people who run mainframes, not people who sell pipelines
Form not loading? Open it in a new tab.
This guide is straightforward and unbiases. At Zetaly, we specialize in creating software that utilizes mainframe data, so we have a deep understanding of the underlying infrastructure. However, the purpose of this guide is to provide you with the information you need to make an informed decision, whether that's to adopt our solution or not. We want to help you weigh your options and choose the best path for your needs
No. OpenTelemetry (OTel) is a standard for transporting operational data, not a monitoring product. It has no storage, dashboards, or alerting. Mainframe monitors, analytics platforms, and OTel pipelines solve different problems; the real question is which combination fits your organization.
Not natively. No stable OpenTelemetry software development kit exists for COBOL or PL/I. On the mainframe, OpenTelemetry data comes from the infrastructure: the operating system, subsystems such as CICS, IMS, MQ and Db2, or data platforms that translate SMF records. The applications themselves cannot participate directly.
It can. Software running on the mainframe consumes capacity that IBM meters, and heavy on-platform processing shows up in billing. When you evaluate any telemetry approach, ask where the processing runs and what its measured on-mainframe footprint is. The difference between architectures is large
No. The underlying need, to collect once, enrich the data, and make it usable beyond the mainframe team, can be met today without OpenTelemetry, and OpenTelemetry alone does not meet it: it transports data but does not keep or interpret it. Adopt the standard when your organization runs OpenTelemetry infrastructure with named consumers.
A clear read and a framework you can use the same day.