Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
  • Loading branch information
cswatt and buraizu authored Jul 23, 2024
1 parent 362bba5 commit dec6e08
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion aerospike/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ To configure this check for an Agent running on a host:

#### Containerized

For containerized environments, See [Configure integrations with Autodiscovery on Kubernetes][5] or [Configure integrations with Autodiscovery on Docker][14] for guidance on applying the parameters below. See the [sample aerospike.d/conf.yaml][3] for all available configuration options.
For containerized environments, see [Configure integrations with Autodiscovery on Kubernetes][5] or [Configure integrations with Autodiscovery on Docker][14] for guidance on applying the parameters below. See the [sample aerospike.d/conf.yaml][3] for all available configuration options.

##### Metric collection

Expand Down
2 changes: 1 addition & 1 deletion istio/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ These are both run as `istio` Agent checks, but they have different responsibili

The default [`istio.d/auto_conf.yaml`][9] file automatically sets up monitoring for each of the `istio-proxy` sidecar containers. The Agent initializes this check for each sidecar container that it detects automatically. This configuration enables the reporting of `istio.mesh.*` metrics for the data exposed by each of these sidecar containers.

To customize data plane portion of the integration:
To customize the data plane portion of the integration:

1. Create a `conf.d/istio.d/conf.yaml` file on your host. This file must contain:

Expand Down

0 comments on commit dec6e08

Please sign in to comment.