Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions specs/agents/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`.