Skip to content

Commit c7543e8

Browse files
rashmichandrashekarrashmichandrashekar
committed
remove doc section for sending same metrics to ultiple workspaces
1 parent ca0196a commit c7543e8

File tree

1 file changed

+1
-167
lines changed

1 file changed

+1
-167
lines changed

‎articles/azure-monitor/containers/prometheus-metrics-multiple-workspaces.md

Lines changed: 1 addition & 167 deletions
Original file line numberDiff line numberDiff line change
@@ -8,174 +8,8 @@ ms.reviewer: aul
88

99
# Send Prometheus metrics to multiple Azure Monitor workspaces
1010

11-
Routing metrics to more Azure Monitor workspaces can be done through the creation of additional data collection rules. All metrics can be sent to all workspaces or different metrics can be sent to different workspaces.
11+
Routing metrics to more Azure Monitor workspaces can be done through the creation of additional data collection rules.
1212

13-
## Send same metrics to multiple Azure Monitor workspaces
14-
15-
You can create multiple Data Collection Rules that point to the same Data Collection Endpoint for metrics to be sent to additional Azure Monitor workspaces from the same Kubernetes cluster. In case you have a very high volume of metrics, a new Data Collection Endpoint can be created as well. Please refer to the service limits [document](../service-limits.md) regarding ingestion limits. Currently, this is only available through onboarding through Resource Manager templates. You can follow the [regular onboarding process](kubernetes-monitoring-enable.md#enable-prometheus-and-grafana) and then edit the same Resource Manager templates to add additional DCRs and DCEs (if applicable) for your additional Azure Monitor workspaces. You'll need to edit the template to add an additional parameters for every additional Azure Monitor workspace, add another DCR for every additional Azure Monitor workspace, add another DCE (if applicable), add the Monitor Reader Role for the new Azure Monitor workspace and add an additional Azure Monitor workspace integration for Grafana.
16-
17-
- Add the following parameters:
18-
```json
19-
"parameters": {
20-
"azureMonitorWorkspaceResourceId2": {
21-
"type": "string"
22-
},
23-
"azureMonitorWorkspaceLocation2": {
24-
"type": "string",
25-
"defaultValue": "",
26-
"allowedValues": [
27-
"eastus2euap",
28-
"centraluseuap",
29-
"centralus",
30-
"eastus",
31-
"eastus2",
32-
"northeurope",
33-
"southcentralus",
34-
"southeastasia",
35-
"uksouth",
36-
"westeurope",
37-
"westus",
38-
"westus2"
39-
]
40-
},
41-
...
42-
}
43-
```
44-
45-
- For high metric volume, add an additional Data Collection Endpoint. You *must* replace `<dceName>`:
46-
```json
47-
{
48-
"type": "Microsoft.Insights/dataCollectionEndpoints",
49-
"apiVersion": "2021-09-01-preview",
50-
"name": "[variables('dceName')]",
51-
"location": "[parameters('azureMonitorWorkspaceLocation2')]",
52-
"kind": "Linux",
53-
"properties": {}
54-
}
55-
```
56-
- Add an additional DCR with the same or a different Data Collection Endpoint. You *must* replace `<dcrName>`:
57-
```json
58-
{
59-
"type": "Microsoft.Insights/dataCollectionRules",
60-
"apiVersion": "2021-09-01-preview",
61-
"name": "<dcrName>",
62-
"location": "[parameters('azureMonitorWorkspaceLocation2')]",
63-
"kind": "Linux",
64-
"properties": {
65-
"dataCollectionEndpointId": "[resourceId('Microsoft.Insights/dataCollectionEndpoints/', variables('dceName'))]",
66-
"dataFlows": [
67-
{
68-
"destinations": ["MonitoringAccount2"],
69-
"streams": ["Microsoft-PrometheusMetrics"]
70-
}
71-
],
72-
"dataSources": {
73-
"prometheusForwarder": [
74-
{
75-
"name": "PrometheusDataSource",
76-
"streams": ["Microsoft-PrometheusMetrics"],
77-
"labelIncludeFilter": {}
78-
}
79-
]
80-
},
81-
"description": "DCR for Azure Monitor Metrics Profile (Managed Prometheus)",
82-
"destinations": {
83-
"monitoringAccounts": [
84-
{
85-
"accountResourceId": "[parameters('azureMonitorWorkspaceResourceId2')]",
86-
"name": "MonitoringAccount2"
87-
}
88-
]
89-
}
90-
},
91-
"dependsOn": [
92-
"[resourceId('Microsoft.Insights/dataCollectionEndpoints/', variables('dceName'))]"
93-
]
94-
}
95-
```
96-
97-
- Add an additional Data Collection Rule Association (DCRA) with the relevant Data Collection Rule (DCR). This associates the DCR with the cluster. You must replace `<dcraName>`:
98-
```json
99-
{
100-
"type": "Microsoft.Resources/deployments",
101-
"name": "<dcraName>",
102-
"apiVersion": "2017-05-10",
103-
"subscriptionId": "[variables('clusterSubscriptionId')]",
104-
"resourceGroup": "[variables('clusterResourceGroup')]",
105-
"dependsOn": [
106-
"[resourceId('Microsoft.Insights/dataCollectionEndpoints/', variables('dceName'))]",
107-
"[resourceId('Microsoft.Insights/dataCollectionRules', variables('dcrName'))]"
108-
],
109-
"properties": {
110-
"mode": "Incremental",
111-
"template": {
112-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
113-
"contentVersion": "1.0.0.0",
114-
"parameters": {},
115-
"variables": {},
116-
"resources": [
117-
{
118-
"type": "Microsoft.ContainerService/managedClusters/providers/dataCollectionRuleAssociations",
119-
"name": "[concat(variables('clusterName'),'/microsoft.insights/', variables('dcraName'))]",
120-
"apiVersion": "2021-09-01-preview",
121-
"location": "[parameters('clusterLocation')]",
122-
"properties": {
123-
"description": "Association of data collection rule. Deleting this association will break the data collection for this AKS Cluster.",
124-
"dataCollectionRuleId": "[resourceId('Microsoft.Insights/dataCollectionRules', variables('dcrName'))]"
125-
}
126-
}
127-
]
128-
},
129-
"parameters": {}
130-
}
131-
}
132-
```
133-
- Add an additional Grafana integration:
134-
```json
135-
{
136-
"type": "Microsoft.Dashboard/grafana",
137-
"apiVersion": "2022-08-01",
138-
"name": "[split(parameters('grafanaResourceId'),'/')[8]]",
139-
"sku": {
140-
"name": "[parameters('grafanaSku')]"
141-
},
142-
"location": "[parameters('grafanaLocation')]",
143-
"properties": {
144-
"grafanaIntegrations": {
145-
"azureMonitorWorkspaceIntegrations": [
146-
// Existing azureMonitorWorkspaceIntegrations values (if any)
147-
// {
148-
// "azureMonitorWorkspaceResourceId": "<value>"
149-
// },
150-
// {
151-
// "azureMonitorWorkspaceResourceId": "<value>"
152-
// },
153-
{
154-
"azureMonitorWorkspaceResourceId": "[parameters('azureMonitorWorkspaceResourceId')]"
155-
},
156-
{
157-
"azureMonitorWorkspaceResourceId": "[parameters('azureMonitorWorkspaceResourceId2')]"
158-
}
159-
]
160-
}
161-
}
162-
}
163-
```
164-
- Assign `Monitoring Data Reader` role to read data from the new Azure Monitor Workspace:
165-
166-
```json
167-
{
168-
"type": "Microsoft.Authorization/roleAssignments",
169-
"apiVersion": "2022-04-01",
170-
"name": "[parameters('roleNameGuid')]",
171-
"scope": "[parameters('azureMonitorWorkspaceResourceId2')]",
172-
"properties": {
173-
"roleDefinitionId": "[concat('/subscriptions/', variables('clusterSubscriptionId'), '/providers/Microsoft.Authorization/roleDefinitions/', 'b0d8363b-8ddd-447d-831f-62ca05bff136')]",
174-
"principalId": "[reference(resourceId('Microsoft.Dashboard/grafana', split(parameters('grafanaResourceId'),'/')[8]), '2022-08-01', 'Full').identity.principalId]"
175-
}
176-
}
177-
178-
```
17913
## Send different metrics to different Azure Monitor workspaces
18014

18115
If you want to send some metrics to one Azure Monitor workspace and other metrics to a different one, follow the above steps to add additional DCRs. The value of `microsoft_metrics_include_label` under the `labelIncludeFilter` in the DCR is the identifier for the workspace. To then configure which metrics are routed to which workspace, you can add an extra pre-defined label, `microsoft_metrics_account` to the metrics. The value should be the same as the corresponding `microsoft_metrics_include_label` in the DCR for that workspace. To add the label to the metrics, you can utilize `relabel_configs` in your scrape config. To send all metrics from one job to a certain workspace, add the following relabel config:

0 commit comments

Comments
 (0)