Forum Discussion
MQTT Events debugging
- 7 months ago
Hello TePeBox ,
Welcome to this Microsoft Fabric community forum.
Your messages are passed on by the HiveMQ MQTT broker to Eventstream (as a subscriber).
Can you get a client like MQTT Explorer or MQTTX connected to the same topics on the HiveMQ MQTT Broker?
If so, you should be able to peek at the messages being generated and it should look like JSON.
If this is also the case, copy one or more of these messages and test them online (it the messages do not contain sensitive data) like https://jsonlint.com/
This will check the JSON format of your messages.
Next to that, do you know Azure is offering a great MQTT broker, part of Azure Event Grid Namespace? Notice that security is based on certificates. Check out this blog post for details.
--
If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated.
So it turned out to be what lbendlin mentioned, the data was not JSON as I expected. I couldn't believe but it was true. And Kudos to svelde which pointed me in the right direction to analyze that.
Perhaps I'll go and add an idea, still the "debugging" of the Eventstreams is a pain. If there would be a way how to really look at the source events as they flow in (before parsing) the issue would have been solved in minutes. Now I had to connect with 3rd party solutions looking into the stream to fix it. Doable, but a lot of work. I found out some other glitches which make Eventstreams really hard to handle, will add ideas around that as well. But we can close this for now.