Skip to content

Commit 499fa34

Browse files
Merge pull request #279446 from yossi-y/main
Pricing clarification
2 parents c879e42 + 2b2ea33 commit 499fa34

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/logs/logs-dedicated-clusters.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Monitor Logs Dedicated Clusters
33
description: Customers meeting the minimum commitment tier could use dedicated clusters
44
ms.topic: conceptual
55
ms.reviewer: yossiy
6-
ms.date: 04/21/2024
6+
ms.date: 06/21/2024
77
ms.custom: devx-track-azurepowershell, devx-track-azurecli
88
---
99

@@ -24,7 +24,7 @@ eligible for commitment tier discount.
2424
- **[Ingest from Azure Event Hubs](../logs/ingest-logs-event-hub.md)** - Lets you ingest data directly from an event hub into a Log Analytics workspace. Dedicated cluster lets you use capability when ingestion from all linked workspaces combined meet commitment tier.
2525

2626
## Cluster pricing model
27-
Log Analytics Dedicated Clusters use a commitment tier pricing model of at least 100 GB/day. Any usage above the tier level incurs charges based on the per-GB rate of that commitment tier. See [Azure Monitor Logs pricing details](cost-logs.md#dedicated-clusters) for pricing details for dedicated clusters. The commitment tiers have a 31-day commitment period from the time a commitment tier is selected.
27+
Log Analytics dedicated clusters have a pricing model based on a commitment tier of minimum 100 GB/day, that applies to data sent to Analytics plan. Ingestion above the tier level incurs charges based on the per-GB rate of that commitment tier. See [Azure Monitor Logs pricing details](cost-logs.md#dedicated-clusters) for pricing details for dedicated clusters. The commitment tiers have a 31-day commitment period from the time a commitment tier is selected.
2828

2929
## Prerequisites
3030

@@ -404,7 +404,7 @@ After you create your cluster resource and it's fully provisioned, you can edit
404404
- **Identity** - The identity used to authenticate to your Key Vault. This can be System-assigned or User-assigned.
405405
- **billingType** - Billing attribution for the cluster resource and its data. Includes on the following values:
406406
- **Cluster (default)**--The costs for your cluster are attributed to the cluster resource.
407-
- **Workspaces**--The costs for your cluster are attributed proportionately to the workspaces in the Cluster, with the cluster resource being billed some of the usage if the total ingested data for the day is under the commitment tier. See [Log Analytics Dedicated Clusters](./cost-logs.md#dedicated-clusters) to learn more about the cluster pricing model.
407+
- **Workspaces**--The costs for your cluster are attributed proportionately to the workspaces in the Cluster, with the cluster resource being billed some of the usage if the total ingested data for the day is under the commitment tier. See [Log Analytics dedicated clusters](./cost-logs.md#dedicated-clusters) to learn more about the cluster pricing model.
408408

409409

410410
>[!IMPORTANT]

0 commit comments

Comments
 (0)