Usage reporting for Data Activator is now live

[garezni]

The Data Activator team has rolled out usage reporting to help you better understand your capacity consumption and future charges. When you look at the Capacity Metrics App you’ll now see operations for the reflex items included.

Our usage reporting is based on the following four meters:

Rule uptime per hour: This is a flat base charge. As long as the rule is active, the account is charged an hourly uptime cost.

Event ingestion: This is accrued when an activator processes incoming real time events data. On the other hand, Activator alerts set on top of Power BI reports don’t carry Ingestion costs.

Event computations: This is accrued when Activator evaluates an incoming event’s data to see whether the defined condition is met. This cost is calculated based on the compute resources your activator consumes in order to evaluate the rule. If the condition is met, the specified action is taken.

Storage: All events stored within Fabric storage incur Fabric storage costs.

You can begin reviewing and tracking your Data Activator capacity usage starting now.  The formal billing for Data Activator usage will begin on Nov 18.  Beforehand, in your usage reporting, you’ll see the operations listed as “non-billable.”

Your resource consumption is calculated in Capacity Units (per second). Use Fabric Capacity Metrics to review your usage and CU consumption.

Please note:

• High volume event ingestion can cause significant resource consumption. To reduce cost, we recommend reviewing the number of events streamed to your Data Activator items. Sometimes the frequency or the volume of events can be reduced without impacting the business outcomes.
• Event computations can be straightforward, such as evaluating each incoming event and responding accordingly. However, Real-Time Intelligence Activator really shines in handling more complex and computationally intensive scenarios. For example, it can act on an event comparing to the system's previous state or perform calculations based on data from multiple events. These state-based event computations are more resource-intensive and thus more expensive.
• Active rules incur costs even if there is no data ingested into them. We recommend making sure you don’t have stale or redundant rules active in the system. Stop or remove your test rules to preserve your capacity.

Please reach out to us via our community page if you have questions or concerns about your Activator resource consumption.

Stay tuned for a detailed blog post about all billing aspects of Real-Time Intelligence coming at Ignite.