-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace deprecated apm settings #2274
Replace deprecated apm settings #2274
Conversation
tracing.apm.* settings were deprecated in 8.14.0 in favor of the new telemetry.* settings. Use the new settings starting with 8.14.0. Old settings will be removed in 9.0.
Not sure about adding also the user setting |
With that new naming, it is true that is like agnostic of the service/implementation used, but at least, currently the stack requires APM service for this to work. So, maybe it could be kept as Just to give some other example, I remember that I required to configure APM (enabled |
telemetry.tracing.enabled: true | ||
telemetry.agent.server_url: "http://fleet-server:8200" | ||
telemetry.agent.environment: "dev" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
💚 Build Succeeded
History
cc @jsoriano |
test integrations |
Created or updated PR in integrations repository to test this version. Check elastic/integrations#12116 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
tracing.apm.*
settings were deprecated in 8.14.0 in favor of the newtelemetry.*
settings. Use the new settings starting with 8.14.0.Old settings will be removed in 9.0.
See elastic/elasticsearch#104908.