Skip to content

Commit 8e68ad0

Browse files
committed
updated agent and prometheus articles
1 parent 0d88875 commit 8e68ad0

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

articles/azure-monitor/insights/container-insights-manage-agent.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,13 @@ To disable collection of environmental variables on a new or existing container,
6060
value: "False"
6161
```
6262

63-
Run the following command to apply the change to Kubernetes clusters other than Azure Red Hat OpenShift): `kubectl apply -f <path to yaml file>`. To edit and apply to Azure Red Hat OpenShift, follow the steps [here](container-insights-prometheus-integration.md#configure-and-deploy-configmaps).
63+
Run the following command to apply the change to Kubernetes clusters other than Azure Red Hat OpenShift): `kubectl apply -f <path to yaml file>`. To edit ConfigMap and apply this change for Azure Red Hat OpenShift clusters, run the command:
64+
65+
``` bash
66+
oc edit configmaps container-azm-ms-agentconfig -n openshift-azure-logging
67+
```
68+
69+
This opens your default text editor. After setting the variable, save the the file in the editor.
6470

6571
To verify the configuration change took effect, select a container in the **Containers** view in Azure Monitor for containers, and in the property panel, expand **Environment Variables**. The section should show only the variable created earlier - **AZMON_COLLECT_ENV=FALSE**. For all other containers, the Environment Variables section should list all the environment variables discovered.
6672

articles/azure-monitor/insights/container-insights-prometheus-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ Perform the following steps to configure your ConfigMap configuration file for K
175175
176176
The configuration change can take a few minutes to finish before taking effect, and all omsagent pods in the cluster will restart. The restart is a rolling restart for all omsagent pods, not all restart at the same time. When the restarts are finished, a message is displayed that's similar to the following and includes the result: `configmap "container-azm-ms-agentconfig" created`.
177177
178-
You can view the updated ConfigMap by running the command, `oc describe configmaps container-azm-ms-agentconfig -n openshift-azure-logging`.
178+
You can view the updated ConfigMap for Azure Red Hat OpenShift by running the command, `oc describe configmaps container-azm-ms-agentconfig -n openshift-azure-logging`.
179179
180180
## Applying updated ConfigMap
181181

0 commit comments

Comments
 (0)