Currently, we have enabled the Distributed Tracing in DEV environment and its all working fine . The authentication used in DEV is Internal Database. However, the same configuration is not working in QA, as we are using LDAP based authentication in Solace Broker. Below is the error observed in the…

Hey @Dhanusri - the issue here is that your LDAP user is not associated to the newly created telemetry ACL and Client profiles, which is a requirement for the Solace receiver in the collector. The error you are receiving is mainly due to either: LDAP user is using the default acl and client pr…

How to integrate Otel Solace Receiver with LDAP based Solace PubSub Event broker 10.4.121

PubSub+ Event Broker

Dhanusri September 25, 2024, 6:00am 3

Hi @Tamimi ,

Thanks much for the response.

Post assigning the #telemetry acl and client profile to the LDAP user, the Otel solace receiver is up and successfully connecting to the broker.

Topic		Replies	Views
Unable to connect with solace using amqps protocols with OAuth PubSub+ Event Broker java , amqp	4	431	February 23, 2023
Enable Distributed Tracing PubSub+ Event Broker	1	72	January 9, 2023
Encountered sasl exception when connecting to Solace topic with AMQPLite dotnet library(AMQP 1.0) PubSub+ Event Broker amqp , c	1	148	February 1, 2024
Spring cloud stream solace + Solace distributed tracing Connectors & Integrations spring-cloud-stream , distributed-tracing , tracing	3	125	September 5, 2024
cannot establish connection to broker after changing the client username PubSub+ Event Portal security , broker	7	1228	September 22, 2020

How to integrate Otel Solace Receiver with LDAP based Solace PubSub Event broker 10.4.121

Related topics