Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Activator is part of Microsoft Fabric Real-Time Intelligence. Similar to other workloads in Fabric, Activator billing is based on the consumption of resources. Fabric uses Capacity Units (CU) to measure and bill for resource usage. You can review and track your Activator capacity usage with the Capacity Metrics App.
Your Azure subscription bill is calculated from your accumulated usage and is reported in the global Real-Time Intelligence capacity consumption metrics. Usage is broken down to the dedicated operations emitted and reported by each Fabric workload and component.
Rule uptime per hour is a flat base charge. As long as a rule is active in your Fabric capacity, it incurs an hourly uptime consumption charge.
Event ingestion accrues when an activator processes incoming real-time event data.
Event computations is the cost of evaluating an incoming event’s data to see whether the defined condition is met. This cost is calculated based on the compute resources the activator consumes in order to evaluate the rule. If the condition is met, the specified rule is activated.
Storage: is the cost of retaining Fabric items and events. All events are retained for 30 days and are stored within Fabric, incurring corresponding Fabric storage costs.
Usage categories
Activator capacity consumption is broken into two categories: interactive and background. Interactive usage consumes resources when the user is actively working within the Fabric UI. Background usage consumes processing resources once a rule starts.
Use the Capacity Metrics App to observe types of operations, their duration, and the percentage of the capacity consumed.
The consumed CUs are aggregated per activator based on its operations.
Background consumption
Activator background capacity consumption is calculated based on the following operations.
| Azure metric name | Fabric operation name | Unit of measure | Fabric consumption rate CU(hr) |
|---|---|---|---|
| Real-Time Intelligence event listener and alert | rule uptime per hour | per hour | 0.02222 |
| Real-Time Intelligence event operations | event ingestion | per event | 0.000011111 |
| Activator event analytics | event computations | per computation | 0.00000278 |
| n/a | storage | per GB per hour | 0.00177 |
Interactive consumption
You pay for interactive capacity consumption activities at a fraction of the background operation cost. Interactive capacity consumption includes activities like exploring the data, reviewing events, viewing visualized activations, and performing other data-related activities to define rules for the Activator.
Pause and resume activity in your capacity
Microsoft Fabric administrators can pause and resume their capacities. When your capacity isn't operational, pause it to save costs for your organization. Later, when you want to resume work, reactivate your capacity.
Important
Pausing or stopping a rule doesn't stop the event listener. The event listener continues to run and incur capacity consumption until the rule is removed. To completely stop all consumption for a rule, you must delete it.
High consumption
If you're the Capacity administrator, take these extra steps to reduce capacity consumption and lower expenses.
High-volume event ingestion can cause significant resource consumption. To reduce costs, review the number of events streamed to the Activator items. Sometimes you can reduce the frequency or the volume of events without impacting the business outcomes.
Event computations can be straightforward, such as evaluating each incoming event and responding accordingly. Real-Time Intelligence Activator also supports complex and computationally intensive scenarios. For example, it can look back on previous events to assess state changes or perform calculations based on data from multiple events. These state-based event computations are more resource-intensive and thus more expensive. Assess the business justification for complex events and remove unnecessary events.
Active rules incur costs even if no data is ingested into them. Ensure that the system has no stale or redundant active rules.
To save computational costs, stop or remove your test rules. If you pause or stop a rule, the event listener doesn't stop. The event listener continues to run and incur capacity consumption (rule uptime per hour) until you remove the rule.
Considerations and limitations
Consumption rates are subject to change at any time. Microsoft uses reasonable efforts to provide notice via email or through in-product notification. Changes take effect on the date stated in Microsoft’s Release Notes or in the Microsoft Fabric blog. If any change to a Microsoft Fabric workload consumption rate materially increases the Capacity Units (CU) required to use a particular workload, you can use the cancellation options available for the chosen payment method.