From 51f2eee9838e9f4ab9412b904b6a0063456768d5 Mon Sep 17 00:00:00 2001 From: Sergey Kleyman Date: Wed, 1 Sep 2021 09:49:35 +0300 Subject: [PATCH 1/3] Added Zero-configuration support section --- specs/agents/configuration.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/specs/agents/configuration.md b/specs/agents/configuration.md index d3852aa0..25c78e97 100644 --- a/specs/agents/configuration.md +++ b/specs/agents/configuration.md @@ -112,3 +112,17 @@ 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 initial setup costs per application, +APM agents should not require any configuration to be set +in order to start sending data to a local APM Server. +After the initial onboarding, users can still customize settings +if the defaults aren't fitting +but that should not stand in the way of the initial onboarding process. + +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 a sensible defaults for `service.name` +as well as the `service.version`. From e004e64b6debec21b6ea4ff736aff86ca2ef37c5 Mon Sep 17 00:00:00 2001 From: Sergey Kleyman Date: Wed, 1 Sep 2021 21:19:44 +0300 Subject: [PATCH 2/3] Update specs/agents/configuration.md Co-authored-by: Trent Mick --- specs/agents/configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specs/agents/configuration.md b/specs/agents/configuration.md index 25c78e97..cd95e887 100644 --- a/specs/agents/configuration.md +++ b/specs/agents/configuration.md @@ -124,5 +124,5 @@ but that should not stand in the way of the initial onboarding process. 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 a sensible defaults for `service.name` -as well as the `service.version`. +Furthermore, if it's possible, agents should detect sensible defaults for `service.name` +and `service.version`. From 25b8ee371122cd8d4c8bfa58aa8d010e05b8767a Mon Sep 17 00:00:00 2001 From: Sergey Kleyman Date: Wed, 1 Sep 2021 21:20:28 +0300 Subject: [PATCH 3/3] Update specs/agents/configuration.md Co-authored-by: Colton Myers --- specs/agents/configuration.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/specs/agents/configuration.md b/specs/agents/configuration.md index cd95e887..68115556 100644 --- a/specs/agents/configuration.md +++ b/specs/agents/configuration.md @@ -115,12 +115,9 @@ Agents should implement a [configuration option](https://docs.google.com/spreads ### Zero-configuration support -To decrease initial setup costs per application, -APM agents should not require any configuration to be set -in order to start sending data to a local APM Server. -After the initial onboarding, users can still customize settings -if the defaults aren't fitting -but that should not stand in the way of the initial onboarding process. +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/`.