Skip to content

Commit 4d24333

Browse files
authored
public repo edit
1 parent 92c3587 commit 4d24333

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ A template ConfigMap file is provided that allows you to easily edit it with you
2424
2525
### Data collection settings
2626

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:
2828

2929
| Key | Data type | Value | Description |
3030
|--|--|--|--|
@@ -40,22 +40,22 @@ The following are the settings that can be configured to control data collection
4040

4141
### Metric collection settings
4242

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:
4444

4545
| Key | Data type | Value | Description |
4646
|--|--|--|--|
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`. |
4848

4949
ConfigMaps is a global list and there can be only one ConfigMap applied to the agent. You cannot have another ConfigMaps overruling the collections.
5050

5151
## Configure and deploy ConfigMaps
5252

5353
Perform the following steps to configure and deploy your ConfigMap configuration file to your cluster.
5454

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.
5656

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.
5959
6060
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.
6161

0 commit comments

Comments
 (0)