Forum Discussion
Activator Monitoring features
Hi evrise,
Thanks for reaching out to the Microsoft fabric community forum.
Its a great observation regarding the metadata shown in the Activator UI. At this time, the granular details like "who updated an event", "when it was updated", and "when it was triggered" are only surfaced in the Activator UI and are not yet exposed programmatically through Fabric Monitor, REST APIs, or Azure Log Analytics.
We understand the importance of having this level of audit detail accessible externally, especially for compliance or operational logging. While Fabric Monitor and Log Analytics provide insights for other Fabric activities (e.g., pipeline runs, dataflows, etc.), Data Activator currently does not emit telemetry or logs to these services.
That said, we’ve received similar feedback from other users, and audit logging support for Activator is something the product team is aware of. In the meantime, the best workaround would be manually capturing metadata from the UI or using custom logging in your action logic, if you're triggering external services via Power Automate or webhooks.
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.
Hi, Thanks. It would be nice to record this using custom logic. But its also impossible. Seems the product is still not production ready even its GA over year.
Solved: Get parameters from Activator event - Microsoft Fabric Community
- Anonymous1 year agoNot applicable
Hi evrise,
You are right, there are some current limitations when it comes to auditing and event context extraction within Data Activator. While it's GA, certain enterprise-grade features like programmatic access to event metadata or logging hooks are still in development or under consideration based on user feedback like yours.
At the moment, you're correct that there's no way to extract event parameters or metadata directly from the Activator trigger itself, which does limit the ability to build robust custom logic downstream.
Also if you want to raise any points or issue towards developers I suggest Ideas forum. Here you can raise an idea or upvote for a pending idea. Go through the below link for Ideas Forum.
Best Regards,
Hammad.
- Anonymous1 year agoNot applicable
Hi evrise,
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.- evrise1 year agoAdvocate II
No, We havent as there is no solution right now.