Skip to content

Commit dd96ba8

Browse files
committed
long running comment
1 parent 860b1c0 commit dd96ba8

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
@@ -97,7 +97,7 @@ After you create your cluster resource, you can edit properties such as *sku*, *
9797
Deleted clusters take two weeks to be completely removed. You can have up to seven clusters per subscription and region, five active, and two deleted in past two weeks.
9898

9999
> [!NOTE]
100-
> Cluster creation triggers resource allocation and provisioning. This operation can take a few hours to complete.
100+
> Creating a cluster involves multiple resources and operation typically complete in two hours.
101101
> Dedicated cluster is billed once provisioned regardless data ingestion and it's recommended to prepare the deployment to expedite the provisioning and workspaces link to cluster. Verify the following:
102102
> - A list of initial workspace to be linked to cluster is identified
103103
> - You have permissions to subscription intended for the cluster and any workspace to be linked
@@ -407,8 +407,8 @@ N/A
407407

408408
> [!NOTE]
409409
> - Linking a workspace can be performed only after the completion of the Log Analytics cluster provisioning.
410-
> - Linking a workspace to a cluster involves syncing multiple backend components and cache hydration, which can take up to two hours.
411-
> - When linking a Log Analytics workspace workspace, the workspace billing plan in changed to *LACluster*, and you should remove sku in workspace template to prevent conflict during workspace deployment.
410+
> - Linking a workspace to a cluster involves syncing multiple backend components and cache hydration, which typically complete in two hours.
411+
> - When linking a Log Analytics workspace workspace, the workspace billing plan in changed to *LACluster*, and you should remove SKU in workspace template to prevent conflict during workspace deployment.
412412
> - Other than the billing aspects that is governed by the cluster plan, all workspace configurations and query aspects remain unchanged during and after the link.
413413
414414
You need 'write' permissions to both the workspace and the cluster resource for workspace link operation:

0 commit comments

Comments
 (0)