From cfaf33f69a75ee1ab51090211c41f4c8c865ba70 Mon Sep 17 00:00:00 2001 From: Sergey Kleyman Date: Thu, 2 Sep 2021 22:01:21 +0300 Subject: [PATCH] Added Zero-configuration support section (#499) * Added Zero-configuration support section * Update specs/agents/configuration.md Co-authored-by: Trent Mick * Update specs/agents/configuration.md Co-authored-by: Colton Myers Co-authored-by: Trent Mick Co-authored-by: Colton Myers --- specs/agents/configuration.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/specs/agents/configuration.md b/specs/agents/configuration.md index d3852aa0..68115556 100644 --- a/specs/agents/configuration.md +++ b/specs/agents/configuration.md @@ -112,3 +112,14 @@ Failure to process one config attribute should not affect processing of others. #### Feature flag Agents should implement a [configuration option](https://docs.google.com/spreadsheets/d/1JJjZotapacA3FkHc2sv_0wiChILi3uKnkwLTjtBmxwU), (`CENTRAL_CONFIG`) which lets users disable the central configuration polling. + +### Zero-configuration support + +To decrease onboarding friction, +APM agents should not require any configuration to send data to a local APM Server. +After onboarding, users can customize settings for which the defaults aren't appropriate. + +Agents should be able to auto-detect the APM Server endpoint +by just defaulting to `http://localhost:8200/`. +Furthermore, if it's possible, agents should detect sensible defaults for `service.name` +and `service.version`.