Messaging, Music and Moving Around
Previous articles in this series have shown OpenTelemetry (OTel) Context propagation for Node.js, Go and C/C++ MQ applications. You should read the first article for an introduction and explanation of the scenarios and problems that need solutions.
This (final?) entry discusses JMS applications.
Continue reading “OTel Context Propagation for MQ Applications: part 3 – JMS”This post was last updated on November 20th, 2024 at 08:00 pm
The first article in this series introduced OpenTelemetry (OTel) tracing with IBM MQ. It showed how the trace context can flow when the application is using the MQ Node.JS or Go interfaces. This article carries on the story for OTel context propagation, this time talking about C++ and C applications.
Continue reading “OTel Context Propagation for MQ Applications: part 2 – C/C++”This post was last updated on November 20th, 2024 at 08:01 pm
OpenTelemetry (OTel) tracing relies on context being propagated from one component in an application stack to another. While IBM MQ does have some ability to carry that context with messages, the OTel SDK design does not make that flow automatic. This post shows how we can extract the context for some applications, and then use OTel context propagation techniques to improve the observability of applications using MQ.
In particular in this post, I’ll talk about applications using MQ with the Node.js and Go interfaces.
Continue reading “OTel Context Propagation for MQ Applications”This post was last updated on November 20th, 2024 at 07:28 pm
As I promised in a recent article, I am coming back to the OpenTelemetry topic. This time, it’s going to be about another pillar of the observability requirements – integrating MQ’s metrics with OpenTelemetry.
Continue reading “MQ Metrics with OpenTelemetry”This post was last updated on March 12th, 2024 at 07:27 am
One recent addition to the plethora of observability tools is OpenTelemetry. It attempts to provide a vendor-agnostic set of common APIs, components, interfaces and protocols that enable interoperability between a range of other tools. It deals with three major pillars of telemetry data, the things you often need to look at when monitoring systems: traces (by which it means application-level data flows), metrics, and logs.
There are already ways of tracking messages through an MQ network and beyond, reporting via OpenTelemetry. And I will soon be talking a lot more about MQ metrics and OpenTelemetry. But as an appetiser, this post shows the third piece of the story: logs.
Continue reading “Handling MQ logs and events with OpenTelemetry”This post was last updated on March 14th, 2024 at 06:47 pm
