Distributed Tracing is now Generally Available!
I'm thrilled to announce that Distributed Tracing is now generally available for all customers and prospects. The recent release of PubSub+ 10.2.0 included distributed tracing!
Thanks to all the customers who tried out our early access release of distributed tracing! Our Early Access release of distributed tracing is now complete! We had a record-breaking number of customers asking for this early access release! Thanks again!
If you would like to continue to experience distributed tracing for free, you still can! Distributed tracing in demo mode is available for current and trial customers in 10.2.0! Check it out!
Solace Distributed Tracing is an amazing new capability that pulls back the curtain and lets you understand on an event-by-event basis what is happening to your events as they traverse through the event mesh. It unites the event mesh with the observability tools used today with application performance monitoring and HTTP/REST messaging! Ultimately, it will provide full visibility of your events as they traverse clients & the event mesh for debugging, troubleshooting, event mesh analytics, performance analysis, audit, governance, and non-repudiation among other use cases. We expect to deliver wave upon wave of new distributed tracing capability over the coming releases.
Speaking of which, keep your eyes out for the upcoming early access release of Distributed Tracing with Context Propagation! This time it will be available on Solace Cloud too! Coming soon!
Keep handling those events,
Rob Tomkins
Core Product Manager
Comments
-
Hey everyone,
I've been getting a lot of questions about how to get started configuring Distributed Tracing with the broker. You can find more details on our Solace documentation.
Rob
1 -
@rtomkins - Hi Rob, thanks for pointing to the Solace documentation link.
Per the documentation "Messages published as part of a transaction (local and XA) do not generate trace messages."
Is there a plan to have tracing enabled for messages published in a transaction? If yes, any rough estimate on the timelines?
0 -
@kriishan_anz - Solace expects to deliver local transactions in 10.2.1, XA are further out. Happy to have a discussion about it, if that would help.
Rob
1 -
Some related API release info for JCSMP & JMS support. Other API support coming soon!
Solace PubSub+ Messaging API for Java (JCSMP) 10.17.0
New Features
- JCSMP - Distributed Tracing - Context Propagation
- JCSMP - Provide Ability to NACK a Specific AD Message and Force Redelivery
Release Highlights
- Bug fixes, as detailed in the release notes
Solace PubSub+ OpenTelemetry Integration for Solace JCSMP API 1.0.0
Release Highlights
- A plug-in for the Solace JCSMP API to allow OpenTelemetry to inject tracing context into the SMF message and export traces to an OpenTelemetry Receiver. Thus expanding coverage of Solace Distributed Tracing beyond the broker and into the API.
Solace PubSub+ Messaging API for JMS 10.17.0
New Features
- JMS - Distributed Tracing - Context Propagation
Release Highlights
- Bug fixes, as detailed in the release notes
Solace PubSub+ OpenTelemetry Integration for Solace JMS API 1.0.0
Release Highlights
- A plug-in for the Solace JMS API to allow OpenTelemetry to inject context into the JMS message and export traces to an OpenTelemetry Receiver. It can also be used for auto-instrumentation of JMS send and receive methods through OpenTelemetry's java agent. Thus expanding coverage of Solace Distributed Tracing beyond the broker and into the API.
1 -
@marc Is there any release date planned for the .net libraries to support OpenTelemetry traces?
0 -
Hi @jacobusmeintjes ,
As it currently stands, we expect to release our C and .NET APIs by the end of this week (June 30th) with support for distributed tracing with a potential for them to be released even sooner. I will be sure to update you once the releases are live.
Cheers,
Murat
2 -
Hi @murat will the JavaScript libraries also get updated with OpenTelemetry changes?
0 -
NodeJS support for OTEL libraries is in development & test! I hope to see it roll out in September!
Rob
0 -
@Tamimi -
Hi Tamimi,
I was evaluating Solace distributed tracing and have come across an issue. I am following this Solace Code Lab:
I can configure the tracing and see the consumer bound to the telemetry queue. However, when I run the subscriber jar provided in the Code Labs the consumer on the telemetry queue gets disconnected. I can see the below mentioned error in the OTEL container logs. Is this a known issue?
2023-08-24 11:12:28 2023-08-24T01:12:28.615Z debug solacereceiver@v0.73.0/messaging_service.go:130 Creating new AMQP Session {"kind": "receiver", "name": "solace", "data_type": "traces"}
2023-08-24 11:12:28 2023-08-24T01:12:28.616Z debug solacereceiver@v0.73.0/messaging_service.go:136 Creating new AMQP Receive Link {"kind": "receiver", "name": "solace", "data_type": "traces", "source": "queue://#telemetry-trace"}
2023-08-24 11:12:28 2023-08-24T01:12:28.618Z error solacereceiver@v0.73.0/unmarshaller.go:92 Received message with unsupported topic, an upgrade is required {"kind": "receiver", "name": "solace", "data_type": "traces", "topic": "_telemetry/broker/trace/egress/v1"}
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver.(*solaceTracesUnmarshaller).unmarshal
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver@v0.73.0/unmarshaller.go:92
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver.(*solaceTracesReceiver).receiveMessage
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver@v0.73.0/receiver.go:217
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver.(*solaceTracesReceiver).receiveMessages
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver@v0.73.0/receiver.go:190
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver.(*solaceTracesReceiver).connectAndReceive.func2
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver@v0.73.0/receiver.go:157
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver.(*solaceTracesReceiver).connectAndReceive
2023-08-24 11:12:28 github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver@v0.73.0/receiver.go:165
2023-08-24 11:12:28 2023-08-24T01:12:28.618Z error solacereceiver@v0.73.0/receiver.go:219 Encountered error while unmarshalling message {"kind": "receiver", "name": "solace", "data_type": "traces", "error": "unsupported trace message, upgrade required"}
0 -
@Tamimi - the problem was resolved after upgrading the OTEL collector to version 0.83.
2
