From 8bb1fe45522b6093067f914d58e119582744d418 Mon Sep 17 00:00:00 2001 From: Curtis Robert Date: Wed, 28 Aug 2024 14:18:00 -0700 Subject: [PATCH] [chore][receiver/chrony] Fix readme config references (#34846) The README is referencing a config option as `address`, but it's actually `endpoint`. This incorrect reference was introduced in the [original PR introducing this component](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/12101). Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34839 --- receiver/chronyreceiver/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/receiver/chronyreceiver/README.md b/receiver/chronyreceiver/README.md index 9d8c2893cf4d..7d1b553af819 100644 --- a/receiver/chronyreceiver/README.md +++ b/receiver/chronyreceiver/README.md @@ -25,7 +25,7 @@ By default, the `chrony` receiver will default to the following configuration: ```yaml chrony/defaults: - address: unix:///var/run/chrony/chronyd.sock # The default port by chronyd to allow cmd access + endpoint: unix:///var/run/chrony/chronyd.sock # The default port by chronyd to allow cmd access timeout: 10s # Allowing at least 10s for chronyd to respond before giving up chrony: @@ -36,7 +36,7 @@ chrony: The following options can be customised: -- address (required) - the address on where to communicate to `chronyd` +- endpoint (required) - the address on where to communicate to `chronyd` - The allowed formats are the following - udp://hostname:port - unix:///path/to/chrony.sock (Please note the triple slash) @@ -55,7 +55,7 @@ An example of the configuration is: ```yaml receivers: chrony: - address: unix:///var/run/chrony/chronyd.sock + endpoint: unix:///var/run/chrony/chronyd.sock timeout: 10s collection_interval: 30s metrics: