What it is
Activator (formerly Data Activator) is Fabric's declarative event-action engine. You write rules in plain language ("when temperature in SensorA exceeds 92 for 5 minutes, page the on-call lead"), and Activator handles continuous evaluation and action dispatch.
Trigger sources
- Eventstream output
- Power BI report visuals (turn a chart into a trigger)
- KQL queries running on a schedule
- Custom event ingestion via REST
Actions
- Teams message (channel or DM)
- Power Automate flow (full automation chain)
- Fabric pipeline run (kick off downstream work)
- Email alert
- Operations Agent invocation (for autonomous response)
- Custom webhook
Patterns we deploy
- Capacity throttling early warning. KQL query on the Capacity Metrics tables; Teams alert to the platform team before users feel it.
- OEE drift. Sensor stream → Eventstream → Activator → Teams ping to plant supervisor.
- Power BI usage spikes. Visual-based trigger on a usage chart; Activator alerts the model owner.
- Stockout prevention. Eventhouse query for inventory below threshold → Activator → Operations Agent drafts PO.
Best practices
- Use dwell time. "5 minutes above threshold" avoids the spike-noise problem.
- Route by severity. Teams for low; Power Automate for action; PagerDuty webhook for "wake someone up."
- Always include the why. The Teams message should include the metric value and a link to the dashboard.
- Test in production-shape data. Test rules fail differently than real ones.
Common pitfalls
!
Alert fatigue. Every false-positive trains your team to ignore the next alert. Tune the dwell window aggressively in week one.