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
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 Learn
I hope this information helps. Please do let us know if you have any further queries.
Thank you