Skip to content

Commit eb16086

Browse files
Merge pull request #285827 from bwren/docs-editor/container-insights-data-collec-1724952146
Update container-insights-data-collection-configure.md
2 parents 8f952ef + 2f85bcf commit eb16086

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-monitor/containers/container-insights-data-collection-configure.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -277,9 +277,11 @@ Use the following procedure to configure and deploy your ConfigMap configuration
277277
1. Create a ConfigMap by running the following kubectl command:
278278

279279
```azurecli
280+
kubectl config set-context <cluster-name>
280281
kubectl apply -f <configmap_yaml_file.yaml>
281282
282283
# Example:
284+
kubectl config set-context my-cluster
283285
kubectl apply -f container-azm-ms-agentconfig.yaml
284286
```
285287
@@ -295,7 +297,7 @@ Use the following procedure to configure and deploy your ConfigMap configuration
295297
To verify the configuration was successfully applied to a cluster, use the following command to review the logs from an agent pod.
296298
297299
```azurecli
298-
kubectl logs ama-logs-fdf58 -n kube-system
300+
kubectl logs ama-logs-fdf58 -n kube-system -c ama-logs
299301
```
300302

301303
If there are configuration errors from the Azure Monitor Agent pods, the output will show errors similar to the following:

0 commit comments

Comments
 (0)