You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/monitor/howto-configure-observability.md
+42-33Lines changed: 42 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Observability provides visibility into every layer of your Azure IoT Operations
20
20
## Prerequisites
21
21
22
22
- Azure IoT Operations Preview installed. For more information, see [Quickstart: Deploy Azure IoT Operations Preview to an Arc-enabled Kubernetes cluster](../get-started/quickstart-deploy.md).
23
+
-[Git](https://git-scm.com/downloads) for cloning the repository.
23
24
24
25
## Configure your subscription
25
26
@@ -34,37 +35,51 @@ az provider register -n "Microsoft.AlertsManagement"
34
35
## Install observability components
35
36
The steps in this section install shared monitoring resources and configure your Arc enabled cluster to emit observability signals to these resources. The shared monitoring resources include Azure Managed Grafana, Azure Monitor Workspace, Azure Managed Prometheus, Azure Log Analytics, and Container Insights.
36
37
37
-
To deploy, run the following command. Use the subscription ID and resource group of your Arc-enabled cluster that you want to monitor.
38
+
1. In your console, navigate to a local folder where you want to clone the Azure IoT Operations repo:
39
+
> [!NOTE]
40
+
> The repo contains the deployment definition of Azure IoT Operations, and samples that include the sample dashboards used in this article.
38
41
39
-
> [!NOTE]
40
-
> To discover other optional parameters you can set, see the [bicep file](https://github.com/Azure/azure-iot-operations/blob/main/tools/setup-3p-obs-infra/observability-full.bicep). The optional parameters can specify things like alternative locations for cluster resources.
42
+
1. Clone the repo to your local machine, using the following command:
41
43
42
-
```azurecli
43
-
az deployment group create \
44
-
--subscription <subscription-id> \
45
-
--resource-group <cluster-resource-group> \
46
-
--template-file observability-full.bicep \
47
-
--parameters grafanaAdminId=$(az ad user show --id $(az account show --query user.name --output tsv) --query=id --output tsv) \
The previous command grants admin access for the newly created Grafana instance to the user who runs it. If that access isn't what you want, run the following command instead. You need to set up permissions manually before anyone can access the Grafana instance.
48
+
1. Navigate to the following path in your local copy of the repo:
To set up permissions manually, [add a role assignment](../../managed-grafana/how-to-share-grafana-workspace.md#add-a-grafana-role-assignment) to the Grafana instance for any users who should have access. Assign one of the Grafana roles (Grafana Admin, Grafana Editor, Grafana Viewer) depending on the level of access desired.
52
+
1. To deploy the observability components, run the following command. Use the subscription ID and resource group of your Arc-enabled cluster that you want to monitor.
53
+
54
+
> [!NOTE]
55
+
> To discover other optional parameters you can set, see the [bicep file](https://github.com/Azure/azure-iot-operations/blob/main/tools/setup-3p-obs-infra/observability-full.bicep). The optional parameters can specify things like alternative locations for cluster resources.
56
+
57
+
```azurecli
58
+
az deployment group create \
59
+
--subscription <subscription-id> \
60
+
--resource-group <cluster-resource-group> \
61
+
--template-file observability-full.bicep \
62
+
--parameters grafanaAdminId=$(az ad user show --id $(az account show --query user.name --output tsv) --query=id --output tsv) \
The previous command grants admin access for the newly created Grafana instance to the user who runs it. If that access isn't what you want, run the following command instead. You need to set up permissions manually before anyone can access the Grafana instance.
To set up permissions manually, [add a role assignment](../../managed-grafana/how-to-share-grafana-workspace.md#add-a-grafana-role-assignment) to the Grafana instance for any users who should have access. Assign one of the Grafana roles (Grafana Admin, Grafana Editor, Grafana Viewer) depending on the level of access desired.
68
83
69
84
If the deployment succeeds, a few pieces of information are printed at the end of the command output. The information includes the Grafana URL and the resource IDs for both the Log Analytics and Azure Monitor resources that were created. The Grafana URL allows you to navigate to the Grafana instance that you configure in [Deploy dashboards to Grafana](#deploy-dashboards-to-grafana). The two resource IDs enable you to configure other Arc enabled clusters by following the steps in [Add an Arc-enabled cluster to existing observability infrastructure](howto-add-cluster.md).
70
85
@@ -134,15 +149,9 @@ Azure IoT Operations provides a collection of dashboards designed to give you ma
134
149
135
150
Complete the following steps to install the Azure IoT Operations curated Grafana dashboards.
136
151
137
-
1. Clone the Azure IoT Operations repo by using the following command:
1. Sign in to the Grafana console, then in the upper right area of the Grafana application, select the **+** icon
144
153
145
-
1. Select **Import dashboard**, follow the prompts to browse to the *samples\grafana-dashboards* path in your cloned copy of the repo, and select a JSON dashboard file
154
+
1. Select **Import dashboard**, follow the prompts to browse to the *samples\grafana-dashboards* path in your local cloned copy of the repo, and select a JSON dashboard file
146
155
147
156
1. When the application prompts, select your managed Prometheus data source
0 commit comments