Forum Discussion
Event Schema Inside Eventstream Never Matching
- 4 months ago
Gotcha. Appreciate that.
Turns out though, the issue isn't a mismatch. As I suspected, the fields match. The problem is that I am not sending the required headers, which unfortunately are not yet documented by Microsoft. The Event Schemas use the Cloud Events spec, so we need to send ce_type and a few others. My contact at MS is working on getting a list of which headers are required.
- 4 months ago
Okay so for anyone else stumbling on this. If you are trying to use Event Schemas inside event streams, you basically can't yet. There are HTTP headers that are required, and they are currently undocumented. I am working with Microsoft now to get a list of the required headers, and I'll update this post when I get that.
Hi Kelderic ,
To view the diagnostics for schema mismatches, open your Event stream, click on the Event stream item in the canvas, and check the bottom pane. Switch to the Runtime logs tab or the Data insights tab, these show ingestion errors, deserialization failures, and runtime validation issues that usually explain why events get marked as Unknown schema despite the preview looking correct.Currently, Event stream health and error logs are available only inside the Event stream editor UI (Runtime logs / Data Insights)
Monitor the Status and Performance of an Eventstream - Microsoft Fabric | Microsoft Learn
Thank you.
Gotcha. Appreciate that.
Turns out though, the issue isn't a mismatch. As I suspected, the fields match. The problem is that I am not sending the required headers, which unfortunately are not yet documented by Microsoft. The Event Schemas use the Cloud Events spec, so we need to send ce_type and a few others. My contact at MS is working on getting a list of which headers are required.
- v-sshirivolu4 months agoCommunity Support
Hi Kelderic ,
Thank you for sharing your findings.
It’s now clear that the issue isn’t caused by a schema mismatch, but by missing required headers such as ce_type when sending events. Since these headers aren’t well documented, it’s leading to confusion with Eventstream validation.
Thanks for reaching out to Microsoft, please let us know if you receive any updates, as this could help others facing the same issue.