An Azure Data Explorer cluster is a pair of engine and data management clusters which uses several Azure resources such as Azure Linux VM’s and Storage. The applicable VMs, Azure Storage, Azure Networking and Azure Load balancer costs are billed directly to the customer subscription.
Azure Data Explorer clusters are billed on a per minute basis. Azure Data Explorer charges you for each VM in the cluster as well as Azure Data Explorer markup for some components of a cluster. Azure Data Explorer markup is proportional to the number of the VM vCores running in the engine cluster.
Azure Data Explorer in now Generally Available and the Azure Data Explorer Markup price below reflects GA price.
|Azure Data Explorer markup||￥ 0.7/core per hour|
Azure Data Explorer offers one types of instance families depending on your workload needs. Storage optimized instances are ideal for workloads that need fewer queries over a large volume of data.
Compute Optimized instances
|Instances||Number of cores||RAM||Temporary Storage||Pricing||Azure Data Explorer Markup|
|D11 v2||2||14 GiB||76 GiB SSD||￥ 1.73/hour
( about ￥ 1,287.12/month )
( about ￥ 1,041.6/month )
|D12 v2||4||28 GiB||153 GiB SSD||￥ 3.46/hour
( about ￥ 2,574.24/month )
( about ￥ 2,083.2/month )
|D13 v2||8||56 GiB||307 GiB SSD||￥ 6.92/hour
( about ￥ 5,148.48/month )
( about ￥ 4,166.4/month )
|D14 v2||16||112 GiB||614 GiB SSD||￥ 13.83/hour
( about ￥ 10,289.52/month )
( about ￥ 8,332.8/month )
What is a Azure Data Explorer Markup?
We charge Azure Data Explorer Markup for fast data ingestion, caching, querying and manageability capability of Azure Data Explorer. The charge is directly proportional to the number of engine vCores in the Azure Data Explorer cluster.
How many nodes run as part of a Azure Data Explorer cluster?
You can choose to run as many engine nodes as you want. The number of engine nodes largely depends on how much data you ingest and your query performance requirements. You can also use Azure Data Explorer’s auto-scale function to dial up and dial down the number of engine nodes. The number and type of data management nodes are auto selected for you depending on your data ingestion needs. Data management nodes are either D3 v2 or D13 v2 VM’s.