Forum Discussion
Deserialization error when publishing events to Eventstream via Event Grid after initial success
- 4 months ago
Hello AditiPattnaik ,
welcome and thank you for your question at the Fabric Community forum.
I see you try to ingest JSON messages in Fabric having an Eventgrid Namespace as source.
Note that you are probably using this source, useful for routing your CloudEvents or MQTT (IoT) messages from Azure Event Grid Namespace to Fabric:
I expect you have configured your Eventgrid Namespace as an MQTT broker already?
It's a bit confusing that you use curl instead of an MQTT client like MQTTX or MQTT Explorer. This I have used several times already.
Can you try this again with an MQTT client as seen in this blog post?
--
If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.
Hello AditiPattnaik ,
welcome and thank you for your question at the Fabric Community forum.
I see you try to ingest JSON messages in Fabric having an Eventgrid Namespace as source.
Note that you are probably using this source, useful for routing your CloudEvents or MQTT (IoT) messages from Azure Event Grid Namespace to Fabric:
I expect you have configured your Eventgrid Namespace as an MQTT broker already?
It's a bit confusing that you use curl instead of an MQTT client like MQTTX or MQTT Explorer. This I have used several times already.
Can you try this again with an MQTT client as seen in this blog post?
--
If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.
We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.
- v-aatheeque3 months ago
Community Support
Hi
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.