Distributed Tracing Enablement

Solace Event Broker
, ,
1

Hello Solace Community,

In our current integration landscape, events are published from SAP S/4HANA Private Cloud to SAP BTP Advanced Event Mesh (public cloud) and then forwarded to Kafka within the customer’s environment through Kafka Connect(preferred by Customer).

We are currently evaluating the implementation of distributed tracing in order to achieve end-to-end runtime visibility across the entire event flow—from S/4HANA through AEM and into Kafka. Our goal is to better monitor event propagation, diagnose performance bottlenecks, and simplify troubleshooting across the different systems involved.

Could anyone share guidance, best practices, or official documentation that explains how to enable and configure distributed tracing for this type of multi-platform event pipeline? Any references, lessons learned from similar implementations would be greatly appreciated.

Thank you in advance for your support.

Regards,

Siva

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Based on the provided documentation, I’ll explain how to configure distributed tracing for a cloud broker in a multi-platform environment involving SAP S/4HANA, SAP BTP Advanced Event Mesh, and Kafka.

Let me break down the key points:

  1. Distributed Tracing Overview:
  • Distributed tracing in Solace Cloud (formerly called PubSub+ Cloud) allows tracking of events from sending application, through event brokers, to receiving application
  • It uses OpenTelemetry specification for generating and collecting trace data
  • The event broker generates trace messages containing spans that represent operations like receiving, sending, moving, or deleting messages
  1. Configuration Components Required:
  • A tracing destination (where trace data will be sent)
  • A telemetry profile (configures how tracing works)
  • Distributed tracing enabled on the event broker service

  1. Configuration Steps:
    For a complete step-by-step configuration, you’ll need to:

  2. Create a tracing destination that supports your observability backend:

    • Solace Insights (if you have a subscription)
    • DataDog
    • OTLP/gRPC endpoint
    • OTLP/HTTP endpoint

  3. Create a telemetry profile with appropriate trace filters and receiver settings

  4. Enable distributed tracing on your event broker service

For the detailed configuration procedure, see Enabling Distributed Tracing.

Important Considerations:

  • The event broker service must be version 10.2.1 or higher
  • A product key is required for production use
  • The solution supports various backends including Datadog, Jaeger, DynaTrace, New Relic, and Grafana
  • For multi-platform environments, ensure proper context propagation is configured
  • Consider performance impacts as distributed tracing generates additional guaranteed messages

For a complete implementation guide and detailed steps, please refer to the Solace documentation on distributed tracing configuration.