Forum Discussion
event trigger authentication & error fetch
Hi fabricpribeiro ,
A gap-detection check is a simple monitoring mechanism that ensures your event-driven pipeline is working correctly end to end. It works by checking whether a pipeline run happens within a defined time after a file is created in OneLake. If a file arrives but no corresponding pipeline execution is detected within that time window, it raises an alert (for example, via email or Teams). This helps you catch issues in the event-to-trigger process such as missed events or Activator failures even when your pipeline never starts and therefore doesn’t generate any logs.
Please check this article for more details:
Reacting to Azure Blob storage events | Microsoft LearnI hope this information helps. Please do let us know if you have any further queries.
Thank you
hi fabricpribeiro ,
Q1) Security / identity
- No extra credential is configured in the trigger UI—security is controlled by Fabric permissions on the source item.
- To subscribe to OneLake events, the trigger owner must have SubscribeOneLakeEvents permission on the source (e.g., Lakehouse).
- If the owner loses that permission, the event subscription can go paused and stop delivering events (retained up to 7 days).
Recommendation: create/own the trigger with a stable non-human identity (SP/workspace identity) and grant only needed permissions.
https://learn.microsoft.com/en-us/fabric/real-time-hub/fabric-events-subscribe-permission
Q2) Logging the event mechanism (pre‑pipeline)
Persist OneLake events
- Capture raw OneLake file/folder events (for example: FileCreated, FileDeleted, FileRenamed, etc.) along with key fields like type, subject, and time.
- Stream these events into storage by creating an Eventstream from OneLake events and landing them into a Lakehouse/Eventhouse so you have a queryable history of “what happened in OneLake and when.”
Persist pipeline Job events
- Subscribe to Fabric Job events to track the pipeline lifecycle (job created / succeeded / failed) as an independent record that a run was actually initiated and how it ended.
Add a gap-detection check
- Build a simple gap check: when a FileCreated event arrives, expect a matching pipeline job created event within N minutes.
- If the job event doesn’t appear in time, raise an alert (Teams/email)—this flags failures in the event-to-trigger mechanism (even when your pipeline-level logging never starts)
https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-trigger-fabric-items
Optionally , you can also stamp your pipeline run metadata with trigger details using built-in trigger parameters like:
@pipeline()?.TriggerEvent?.FileName
https://learn.microsoft.com/en-us/fabric/data-factory/pipeline-runs
https://learn.microsoft.com/en-us/fabric/data-factory/pipeline-runs#event-based-pipeline-runs
Thanks,
Shreya
Hello,
Can you please explain this part better ( I mean, with more verbose, please)?
Add a gap-detection check
- Build a simple gap check: when a FileCreated event arrives, expect a matching pipeline job created event within N minutes.
- If the job event doesn’t appear in time, raise an alert (Teams/email)—this flags failures in the event-to-trigger mechanism (even when your pipeline-level logging never starts)
Hi fabricpribeiro ,
A gap-detection check is a simple monitoring mechanism that ensures your event-driven pipeline is working correctly end to end. It works by checking whether a pipeline run happens within a defined time after a file is created in OneLake. If a file arrives but no corresponding pipeline execution is detected within that time window, it raises an alert (for example, via email or Teams). This helps you catch issues in the event-to-trigger process such as missed events or Activator failures even when your pipeline never starts and therefore doesn’t generate any logs.
Please check this article for more details:
Reacting to Azure Blob storage events | Microsoft LearnI hope this information helps. Please do let us know if you have any further queries.
Thank you