From 95b2ccd08a65d4e4af20b80b5f140a3f2b83220e Mon Sep 17 00:00:00 2001 From: Dmitrii Anoshin Date: Thu, 11 Apr 2024 15:49:13 -0700 Subject: [PATCH] Update exporter/loadbalancingexporter/README.md Co-authored-by: Curtis Robert --- exporter/loadbalancingexporter/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exporter/loadbalancingexporter/README.md b/exporter/loadbalancingexporter/README.md index 8f8c35f437bc..1b34b8696ce0 100644 --- a/exporter/loadbalancingexporter/README.md +++ b/exporter/loadbalancingexporter/README.md @@ -72,7 +72,7 @@ Refer to [config.yaml](./testdata/config.yaml) for detailed examples on using th * `interval` resolver interval in go-Duration format, e.g. `5s`, `1d`, `30m`. If not specified, `30s` will be used. * `timeout` resolver timeout in go-Duration format, e.g. `5s`, `1d`, `30m`. If not specified, `5s` will be used. * `port` port to be used for exporting the traces to the addresses resolved from `service`. By default, the port is set in Cloud Map, but can be be overridden with a static value in this config - * `health_status` filter in AWS Cloud Map, you can specify the health status of the instances that you want to discover. The healthStatus filter is optional and allows you to query based on the health status of the instances. + * `health_status` filter in AWS Cloud Map, you can specify the health status of the instances that you want to discover. The health_status filter is optional and allows you to query based on the health status of the instances. * Available values are * `HEALTHY`: Only return instances that are healthy. * `UNHEALTHY`: Only return instances that are unhealthy.