I am using https://mqttx.app/web-client using anonymous connect, so I don't have permission to publish to any topcis, and when I send a message to topic A, it shows disconnect with unauth and then reconnect. However our live trace shows nothing during this process, shall we also show some reconnect log to our customer? For example, when the client is taken over, shall our customer also aware of that?
There is an MqttSessionAttached event on reconnect, you should be able to see it on Dgrep. Seems the livetrace tool is not stable, sometimes it doesn't show some events on UI.
Describe the bug
I am using https://mqttx.app/web-client using anonymous connect, so I don't have permission to publish to any topcis, and when I send a message to topic A, it shows disconnect with unauth and then reconnect. However our live trace shows nothing during this process, shall we also show some reconnect log to our customer? For example, when the client is taken over, shall our customer also aware of that?