Skip to content
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

[APM] APM agent config created prior to Fleet migration is not injected into integration policy #105383

Closed
axw opened this issue Jul 13, 2021 · 1 comment · Fixed by #105504
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:APM - DEPRECATED Use Team:obs-ux-infra_services. v7.14.0

Comments

@axw
Copy link
Member

axw commented Jul 13, 2021

Kibana: 7.14-SNAPSHOT

If you create APM agent config in the UI, and subsequently run the Fleet ("schema") migration, then the agent config is not injected into the integration policy initially.

Steps to reproduce:

  1. Create a 7.14-SNAPSHOT deployment in cloud QA
  2. Navigate to the APM app in Kibana, create an agent config for "All"

image

  1. Still in the APM app, run Fleet/schema migration ("Switch to data streams")
  2. Navigate to the Fleet app, view the integration policy; it should have the agent config included, but will be missing

image

See also elastic/apm-server#5177 (comment)

@axw axw added bug Fixes for quality problems that affect the customer experience Team:APM - DEPRECATED Use Team:obs-ux-infra_services. v7.14.0 labels Jul 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:APM - DEPRECATED Use Team:obs-ux-infra_services. v7.14.0
Projects
None yet
4 participants