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.

Sign up for GitHub

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

Jump to bottom

APM config for internal ESS clusters is not applied by agent/fleet-server #3526

Open

juliaElastic opened this issue May 7, 2024 · 0 comments

Labels

Team:Elastic-Agent-Control-Plane

Contributor

juliaElastic commented May 7, 2024 •

edited

Loading

We discovered an issue with the default APM config injected by cloud to internal ESS clusters: https://elasticco.atlassian.net/browse/CP-3464

It seems this APM config is not applied on a newly created clusters, and fleet-server traces are not being sent to https://overview.elastic-cloud.com/app/r/s/JIEzg

It is not clear if the issue is on elastic-agent or fleet-server side.

Related doc: https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/dev_docs/apm_tracing.md

Originally posted by @juliaElastic in #3328 (comment)

juliaElastic added the Team:Elastic-Agent-Control-Plane label

michel-laterman mentioned this issue

Run apm-server standalone as part of e2e tests #3728

Draft

8 tasks

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