Learning Library

← Back to Library

OpenTelemetry for Mainframe Observability

Key Points

  • Modern hybrid applications span front‑ends, cloud services, and mainframes, so end‑to‑end visibility is essential for reliable operation.
  • Most organizations rely on four to seven separate monitoring tools, creating a fragmented stack that slows detection, isolation, and resolution of issues.
  • OpenTelemetry, a vendor‑agnostic, CNCF‑governed framework, standardizes the generation, processing, and transmission of metrics, traces, and logs across diverse environments.
  • By instrumenting code (automatically or via OpenTelemetry SDKs) and using the OpenTelemetry Protocol, spans are collected and processed by the OpenTelemetry Collector, which can filter, enrich, and forward data to downstream systems.
  • OpenTelemetry itself is not a product; it integrates with a variety of observability back‑ends and tooling to provide a unified view of system behavior.

Full Transcript

# OpenTelemetry for Mainframe Observability **Source:** [https://www.youtube.com/watch?v=hLvwoow3XTk](https://www.youtube.com/watch?v=hLvwoow3XTk) **Duration:** 00:05:32 ## Summary - Modern hybrid applications span front‑ends, cloud services, and mainframes, so end‑to‑end visibility is essential for reliable operation. - Most organizations rely on four to seven separate monitoring tools, creating a fragmented stack that slows detection, isolation, and resolution of issues. - OpenTelemetry, a vendor‑agnostic, CNCF‑governed framework, standardizes the generation, processing, and transmission of metrics, traces, and logs across diverse environments. - By instrumenting code (automatically or via OpenTelemetry SDKs) and using the OpenTelemetry Protocol, spans are collected and processed by the OpenTelemetry Collector, which can filter, enrich, and forward data to downstream systems. - OpenTelemetry itself is not a product; it integrates with a variety of observability back‑ends and tooling to provide a unified view of system behavior. ## Sections - [00:00:00](https://www.youtube.com/watch?v=hLvwoow3XTk&t=0s) **Untitled Section** - ## Full Transcript
0:00modern applications do not exist in 0:01silos or monolithic technology Stacks 0:04typically today we see front-end 0:06applications triggered perhaps by mobile 0:07devices connecting to cloud services and 0:10then onto other Technologies including 0:12the Mainframe in this video I'm going to 0:15be talking about observability open 0:17Telemetry and how it can relate to the 0:20Mainframe in these applications the 0:23transactions and interactions between 0:24the systems are critical for it 0:26operations to understand endtoend 0:28visibility is key to knowing whe the 0:31hybrid application is performing 0:32correctly most organizations use a 0:35number of monitoring and observability 0:36tools to achieve this however we know 0:39that most organizations actually use 0:41between four and seven different Tools 0:42in order to do this this disjointed 0:46approach means that we end up with uh a 0:48slower process to actually detect 0:50isolate and ultimately resolve it 0:53operational issues to address this 0:55challenge we've seen the emergence of 0:56open Telemetry over the last 5 years so 0:59what is it it we'll put simply open 1:01Telemetry is a vendor agnostic 1:03observability framework that helps with 1:06the generation processing and 1:08transmission of different types of 1:10telemetry data or signals these are 1:18metrics 1:22traces and 1:27logs now what makes open telemetry 1:30different is that unlike a vendor 1:32specific 1:33implementation open Telemetry is an open 1:36framework that is managed by the cloud 1:38native Computing foundation and has 1:40support and contributions from many 1:42different vendors across the IT industry 1:45now we're going to talk about some of 1:46the basic concepts of open Telemetry 1:49first your application or the 1:51environment it's running on needs to be 1:55instrumented this will allow the signals 1:57to be generated in order to observe the 1:59system 2:00this can either be done automatically 2:01depending on the language that you're 2:03using or it might have to be done 2:04manually using sdks provided by open 2:11Telemetry the system will then generate 2:14data in the form of open Telemetry 2:17protocol or 2:19OTP this describes properties of the 2:22system that are being observed and 2:25seen by complying with this standard 2:28different spans from different 2:30Technologies and different systems can 2:32then be later correlated together to 2:33give the full observability view of the 2:38system these spans are sent to the open 2:41Telemetry 2:44collector The Collector is a process 2:47that takes this information and performs 2:50processing on it such as filtering or 2:52maybe enriching the data in some form by 2:54perhaps correlating multiple sources 2:57together it can then be sent on to other 3:01collectors or maybe an observability 3:03back end for visualization and further 3:05analysis so as you instrument all of 3:07these across all these environments we 3:10will now generate the data that allows 3:12the full system to be observed so now we 3:15have all of this Telemetry data and 3:16probably quite a lot of it what do we do 3:18with it this is where the observability 3:21back end comes 3:24in now to be clear open Telemetry itself 3:28is not a product 3:30instead there are many different 3:31software offerings out there both open 3:34source and vendor provided that take OTP 3:37Source data process it and perform 3:39analysis on it this will take data from 3:42multiple from all these sources derive 3:45visualizations and Analysis around 3:48performance and the precise nature of 3:51this analysis varies from product to 3:53product but typically they will provide 3:55an analysis of the application that's 3:57running and the infrastructure that that 3:59it that the application is running on an 4:01obvious example of this would be a trace 4:03view of a critical customer Journey from 4:05a mobile initiated transaction through 4:07the environment to maybe a database 4:09update on the 4:11Mainframe using open Telemetry we can 4:14then enrich that information using 4:16signals from metrics and logs across all 4:18these different environments bringing 4:20them together to give a more complete 4:21view this helps the it operations teams 4:25and site reliability Engineers to more 4:28quickly identify where where a problem 4:30might be if there is a performance issue 4:32isolate it to the particular area that 4:34is impacting it and then taking prompt 4:38action whether that's something they do 4:39themselves or engaging the right subject 4:42matter expert to then take action on 4:44that quickly in this video we've learned 4:46the basics about what open Telemetry is 4:48but we just scratched the surface of 4:49what is possible by exploiting it 4:52observability provides deep 4:53visualization into hybrid applications 4:56that span multiple technology stacks and 4:58provide automated res solutions to 5:00problems within there having a standard 5:03adopted across all these platforms means 5:05that it is easier to integrate that data 5:07and build up that full complete view 5:10this is true for not just new 5:11applications that are written on the 5:13cloud in microservices or containers but 5:16also older applications that might have 5:18been around for many years running on 5:19something like the Mainframe when you 5:21have a complete endtoend view the time 5:24and resources taken to resolve a problem 5:26are greatly 5:28reduced e