As part of the consumption model for KQL Database and Eventhouse, we are enabling public preview for Kusto Cache consumption. This change is scheduled to start rolling out on April 12. This means that you will start seeing billable consumption of the OneLake Cache Data Stored meter from the KQL Database and Eventhouse artifacts. For details on all things KQL Database and Eventhouse consumption check out this article. Here is a quick summary of OneLake Cache Storage:
OneLake Cache Storage: This is your high performance tier that provides the best query performance.
The amount data that is stored in your cache is controlled via your caching policy. To understand how to configure you caching policy chek out this article.
You can monitor how much OneLake Cache storage you are utilizing via the Microsoft Fabric Capacity Metrics App under the storage tab. Usage from KQL Database and Eventhouse will be reported via the KustoCacheStorage Operation Name. The “Billing Type” will change from “Non-billable” to “Billable”.
A newly introduced feature with Eventhouse is the ability to enable minimum consumption. When this is enabled, you will not be charged for cache storage. Instead, it will be included with the always-on capacity of your Eventhouse.
