Skip to content

Commit 70ffca0

Browse files
authored
Update azure-monitor-workspace-overview.md
------- cc: @bwren
1 parent 43b480c commit 70ffca0

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/azure-monitor/essentials/azure-monitor-workspace-overview.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,15 @@ A single Azure Monitor workspace can collect data from multiple sources, but the
3333
> [!NOTE]
3434
> You cannot currently query across multiple Azure Monitor workspaces.
3535
36-
## Workspace limits
37-
These are currently only related to Prometheus metrics, since this is the only data currently stored in Azure Monitor workspaces.
38-
36+
## Workspace design
3937
Many customers will choose an Azure Monitor workspace design to match their Log Analytics workspace design. Since Azure Monitor workspaces currently only contain Prometheus metrics, and metric data is typically not as sensitive as log data, you may choose to further consolidate your Azure Monitor workspaces for simplicity.
4038

39+
## Limitations
40+
See [Azure Monitor service limits](../service-limits.md#prometheus-metrics) for performance related service limits for Azure Monitor managed service for Prometheus.
41+
- Private Links aren't supported for Prometheus metrics collection into Azure monitor workspace.
42+
- Azure monitor managed service for Prometheus is only supported in public clouds.
43+
- Metrics addon doesn't work on AKS clusters configured with HTTP proxy.
44+
- Scraping and storing metrics at frequencies less than 1 second isn't supported.
4145

4246

4347
## Create an Azure Monitor workspace

0 commit comments

Comments
 (0)