Skip to content

Conversation

@SergeyKleyman
Copy link
Contributor

@SergeyKleyman SergeyKleyman commented Sep 1, 2021

Closes #401

@SergeyKleyman SergeyKleyman self-assigned this Sep 1, 2021
@SergeyKleyman SergeyKleyman requested review from a team as code owners September 1, 2021 06:52
@ghost
Copy link

ghost commented Sep 1, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-09-01T18:20:46.092+0000

  • Duration: 3 min 0 sec

  • Commit: 25b8ee3

Trends 🧪

Image of Build Times

Copy link
Contributor

@basepi basepi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a pass at simplifying and clarifying the language a little bit. These are definitely nits, do with them as you will.

Comment on lines +122 to +125
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`.
Copy link
Contributor Author

@SergeyKleyman SergeyKleyman Sep 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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`.
By default, agents should send data to the APM Server at `http://localhost:8200/`.
If possible, agents should detect sensible defaults for `service.name` and `service.version`.
Even if detecting these values is not possible, a default value for `service.name` should be provided for frictionless onboarding.

WDYT about the suggestion above?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks excellent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[META 382] SPEC for Agent's zero-configuration approach

7 participants