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/azure-monitor/insights/container-insights-agent-config.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ A template ConfigMap file is provided that allows you to easily edit it with you
24
24
25
25
### Data collection settings
26
26
27
-
The following are the settings that can be configured to control data collection.
27
+
The following table describes the settings you can configure to control data collection:
28
28
29
29
| Key | Data type | Value | Description |
30
30
|--|--|--|--|
@@ -40,22 +40,22 @@ The following are the settings that can be configured to control data collection
40
40
41
41
### Metric collection settings
42
42
43
-
The following are the settings that can be configured to control metric collection.
43
+
The following table describes the settings you can configure to control metric collection:
44
44
45
45
| Key | Data type | Value | Description |
46
46
|--|--|--|--|
47
-
|`[metric_collection_settings.collect_kube_system_pv_metrics] enabled =`| Boolean | true or false | This setting allows persistent volume (PV) usage metrics to be collected in the kube-system namespace. By default, usage metrics for persistent volumes with persistent volume claims in the kube-system namespace are not collected. When this setting is set to true, PV usage metrics for all namespaces are collected. By default, this is set to false. |
47
+
|`[metric_collection_settings.collect_kube_system_pv_metrics] enabled =`| Boolean | true or false | This setting allows persistent volume (PV) usage metrics to be collected in the kube-system namespace. By default, usage metrics for persistent volumes with persistent volume claims in the kube-system namespace are not collected. When this setting is set to `true`, PV usage metrics for all namespaces are collected. By default, this is set to `false`. |
48
48
49
49
ConfigMaps is a global list and there can be only one ConfigMap applied to the agent. You cannot have another ConfigMaps overruling the collections.
50
50
51
51
## Configure and deploy ConfigMaps
52
52
53
53
Perform the following steps to configure and deploy your ConfigMap configuration file to your cluster.
54
54
55
-
1.[Download](https://github.com/microsoft/Docker-Provider/blob/ci_prod/kubernetes/container-azm-ms-agentconfig.yaml.) the template ConfigMap yaml file and save it as container-azm-ms-agentconfig.yaml.
55
+
1. Download the [template ConfigMap YAML file](https://github.com/microsoft/Docker-Provider/blob/ci_prod/kubernetes/container-azm-ms-agentconfig.yaml) and save it as container-azm-ms-agentconfig.yaml.
56
56
57
-
>[!NOTE]
58
-
>This step is not required when working with Azure Red Hat OpenShift since the ConfigMap template already exists on the cluster.
57
+
>[!NOTE]
58
+
>This step is not required when working with Azure Red Hat OpenShift because the ConfigMap template already exists on the cluster.
59
59
60
60
2. Edit the ConfigMap yaml file with your customizations to collect stdout, stderr, and/or environmental variables. If you are editing the ConfigMap yaml file for Azure Red Hat OpenShift, first run the command `oc edit configmaps container-azm-ms-agentconfig -n openshift-azure-logging` to open the file in a text editor.
0 commit comments