Tag: jaeger

This article discusses a new API Exit that might help to solve a problem experienced by a number of users trying out the MQ Tracing Exit. When that exit is configured, it adds properties to the MQ message to carry OpenTelemetry context data. A receiving application may be surprised to see those properties. So this new exit can remove an unexpected RFH2 structure, allowing the application to continue to run unchanged.

This post was last updated on August 19th, 2026 at 06:51 pm

Previous articles in this series have shown OpenTelemetry (OTel) Context propagation for MQ applications in different languages. You should read the first article for an introduction and explanation of the scenarios and problems that need solutions.

This entry has a couple of additional observations I had when trying different configurations with the MQ Tracing Exit (the Instana-developed component) that’s part of the MQ product.