Thanks all for sharing the information!
We receive a question more often from downstream applications, who are all publishing messages on this topic?
Let’s take the example of a data warehouse application. They just consume messages from a queue endpoint and do not know who is publishing messages to the topic which subscribed to that queue. There is no information about clients who are all publishing messages on that topic in solace pubsub+ manager or in the event.log.
If event.log registers the information of topic or queue name for the ingress or egress flow open it will help us to identify the clients who connected to topics and queues. This will also help us to get stats of the topic (total ingress and egress).
For the application that uses direct transport to publish messages, the topic name can be added in the client_connect even log.
I understand the topics are dynamic and the client connect changes the string every time when it connects. Solace log registers the application connect even in log and if we get the destination name in the same log event it will be a great help.
Thanks!