AWS AmazonCloudWatch documentation change
Summary
Corrected capitalization from 'docker' to 'Docker' in labels and fixed apostrophe usage in possessive forms
Security assessment
Changes are purely grammatical/terminology corrections without any security implications. No vulnerabilities, security features, or security-related configurations are modified or added.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-autodiscovery-ecs.md b/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-autodiscovery-ecs.md index 517780b10..1f9195fd1 100644 --- a//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-autodiscovery-ecs.md +++ b//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-autodiscovery-ecs.md @@ -26 +26 @@ The metadata is used by the CloudWatch agent to scan the Prometheus targets with - * Container docker label-based service discovery + * Container Docker label-based service discovery @@ -139 +139 @@ This section includes examples that demonstrate ECS service discovery. -This example enables docker label-based service discovery. The CloudWatch agent will query the ECS tasks’ metadata once per minute and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. +This example enables Docker label-based service discovery. The CloudWatch agent will query the ECS tasks' metadata once per minute and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. @@ -143 +143 @@ The default value of `sd_port_label` in the `docker_label` section is `ECS_PROME -The default value of `sd_metrics_path_label` in the `docker_label` section is `ECS_PROMETHEUS_METRICS_PATH`. If the container has this docker label, its value will be used as the `__metrics_path__` . If the container does not have this label, the default value `/metrics` is used. +The default value of `sd_metrics_path_label` in the `docker_label` section is `ECS_PROMETHEUS_METRICS_PATH`. If the container has this Docker label, its value will be used as the `__metrics_path__` . If the container does not have this label, the default value `/metrics` is used. @@ -145 +145 @@ The default value of `sd_metrics_path_label` in the `docker_label` section is `E -The default value of `sd_job_name_label` in the `docker_label` section is `job`. If the container has this docker label, its value will be appended as one of the labels for the target to replace the default job name specified in the Prometheus configuration. The value of this docker label is used as the log stream name in the CloudWatch Logs log group. +The default value of `sd_job_name_label` in the `docker_label` section is `job`. If the container has this Docker label, its value will be appended as one of the labels for the target to replace the default job name specified in the Prometheus configuration. The value of this Docker label is used as the log stream name in the CloudWatch Logs log group. @@ -159 +159 @@ The default value of `sd_job_name_label` in the `docker_label` section is `job`. -This example enables docker label-based service discovery. THe CloudWatch agent will query the ECS tasks’ metadata every 15 seconds and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. The containers with a docker label of `ECS_PROMETHEUS_EXPORTER_PORT_SUBSET_A` will be scanned. The value of the docker label `ECS_PROMETHEUS_JOB_NAME` is used as the job name. +This example enables Docker label-based service discovery. THe CloudWatch agent will query the ECS tasks' metadata every 15 seconds and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. The containers with a Docker label of `ECS_PROMETHEUS_EXPORTER_PORT_SUBSET_A` will be scanned. The value of the docker label `ECS_PROMETHEUS_JOB_NAME` is used as the job name. @@ -184 +184 @@ This example enables docker label-based service discovery. THe CloudWatch agent -This example enables ECS task definition ARN regular expression-based service discovery. The CloudWatch agent will query the ECS tasks’ metadata every five minutes and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. +This example enables ECS task definition ARN regular expression-based service discovery. The CloudWatch agent will query the ECS tasks' metadata every five minutes and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. @@ -218 +218 @@ Two task definition ARN regular expresion sections are defined: -This example enables ECS service name regular expression-based service discovery. The CloudWatch agent will query the ECS services’ metadata every five minutes and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. +This example enables ECS service name regular expression-based service discovery. The CloudWatch agent will query the ECS services' metadata every five minutes and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. @@ -248 +248 @@ Two service name regular expresion sections are defined: -This example enables both ECS service discovery modes. The CloudWatch agent will query the ECS tasks’ metadata every 90 seconds and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. +This example enables both ECS service discovery modes. The CloudWatch agent will query the ECS tasks' metadata every 90 seconds and write the discovered targets into the `/tmp/cwagent_ecs_auto_sd.yaml` file within the CloudWatch agent container. @@ -250 +250 @@ This example enables both ECS service discovery modes. The CloudWatch agent will -For the docker-based service discovery configuration: +For the Docker-based service discovery configuration: @@ -252 +252 @@ For the docker-based service discovery configuration: - * The ECS tasks with docker label `MY_PROMETHEUS_EXPORTER_PORT_LABEL` will be filtered for Prometheus port scan. The target Prometheus container port is specified by the value of the label `MY_PROMETHEUS_EXPORTER_PORT_LABEL`. + * The ECS tasks with Docker label `MY_PROMETHEUS_EXPORTER_PORT_LABEL` will be filtered for Prometheus port scan. The target Prometheus container port is specified by the value of the label `MY_PROMETHEUS_EXPORTER_PORT_LABEL`. @@ -256 +256 @@ For the docker-based service discovery configuration: - * The value of the docker label `MY_PROMETHEUS_EXPORTER_PORT_LABEL` is used as the job label. If the container does not have this docker label, the job name defined in the Prometheus configuration is used. + * The value of the docker label `MY_PROMETHEUS_EXPORTER_PORT_LABEL` is used as the job label. If the container does not have this Docker label, the job name defined in the Prometheus configuration is used.