Fabric Data Activator for pipeline monitoring

[Ira_27]

Hello Community, 

We are starting to migrate from our ADF into fabric and have a scenario where we would like to leverage Activator to send pipeline failure alerts. I started to configure Data Activtor but in Fabric events it only lets you choose events by item, is it possible to have all items/jobs monitoried in a single activator and we can then create rules for each specific ones we want to monitor? 

Has anyone been able to achive this, we have hundereds of jobs and this will result in same number of activators which will be cumbersome... 

[burakkaragoz · Accepted solution]

Hi @Ira_27 ,

You're absolutely right in identifying a key limitation in the current implementation of Fabric Data Activator—as of now, it requires you to configure monitoring per item, which can become unmanageable when dealing with hundreds of pipelines or jobs.

🔍 Current Limitation:

• Fabric Events in Data Activator are scoped at the item level, meaning each pipeline or job must be individually selected and monitored.
• This design does not currently support a wildcard or global monitoring scope across all items within a workspace or tenant.

✅ Potential Workarounds:

1. Event Hub or Log Analytics Integration (if available):

   • If your Fabric environment is integrated with Azure Monitor, Log Analytics, or Event Hubs, you might be able to centralize pipeline telemetry and use custom rules or Azure Alerts to monitor failures across all jobs.
   • This would allow you to decouple the alerting logic from the Activator and manage it more scalably.

2. Metadata-Driven Activator Configuration:

   • If Activator configuration can be automated (e.g., via REST API or scripting), you could generate activators programmatically based on metadata (e.g., job names, tags, or failure conditions).
   • This doesn’t eliminate the one-activator-per-job model but makes it more manageable.

3. Use of Tags or Naming Conventions:

   • If Activator supports filtering or grouping by tags or naming patterns (this would need to be confirmed in the latest documentation), you could create broader rules that apply to grouped jobs.

4. Feature Request to Microsoft:

   • This is a strong candidate for a feature enhancement. Submitting feedback via the Fabric Ideas portal or through your Microsoft account team could help prioritize a more scalable solution (e.g., workspace-level or tenant-level monitoring scopes).

🧠 Strategic Recommendation:

For now, consider implementing a hybrid approach:

• Use Activator for critical pipelines where real-time alerting is essential.
• Use centralized logging (e.g., via Azure Monitor or custom logging tables in Fabric) for bulk monitoring and reporting.
• Automate the creation and management of Activators where possible to reduce manual overhead.

[v-mdharahman]

Hi @Ira_27,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you want a way to have all items/jobs monitoried by a single activator and then create rules for each specific ones you want to monitor. As @Rufyda and @andrewsommer both responded to your query, please go through their responses and check if it answers your query.

I would also take a moment to thank @Rufyda and @andrewsommer, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[v-mdharahman]

Hi @Ira_27,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.

If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

[v-mdharahman]

Hi @Ira_27,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.

Thank you.

[Rufyda]

You need to define events for each item (like each pipeline or job) individually.

However, you can use multiple rules within a single Activator to specify which events you want to monitor for each job. Alternatively, you could group jobs together to reduce the number of Activators needed.

If you have hundreds of jobs, you can also integrate Activator with other tools like Logic Apps to organize and manage alerts more efficiently.

If it has, please consider clicking “Accept Answer” and “Yes” if you found the response helpful.
If you still have any questions or need further assistance, feel free to let us know — we're happy to help!

Thank you!

[andrewsommer]

We use the Teams action in the pipeline to send a notification to a Teams channel that is monitored by whoever is on call. 

Please mark this post as solution if it helps you. Appreciate Kudos.