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

[Question]: Conflicts under integration upgrade related to APM integration. #120059

Closed
amolnater-qasource opened this issue Dec 1, 2021 · 7 comments
Assignees
Labels
Question Ticket having question for Dev team Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

Description:
As discussed earlier APM integration was a managed integration like system or endpoint security.
However we had observed some different behaviour.

Kibana Version:
8.0 Snapshot Kibana cloud-staging environment

Queries:

  • If Elastic APM is managed integration it should have upgraded to latest version itself like system or endpoint security.
  • "Keep policies up-to-date automatically" can't be modified by user, but on system or endpoint security we can.

Could please confirm this behaviour as expected and share us update regarding the use case for both the scenarios if expected.

Screenshot:
11

@amolnater-qasource amolnater-qasource added Team:Fleet Team label for Observability Data Collection Fleet team Question Ticket having question for Dev team labels Dec 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@ghost ghost assigned kpollich and EricDavisX and unassigned EricDavisX Dec 1, 2021
@ghost
Copy link

ghost commented Dec 1, 2021

reviewed and assigned to @kpollich
c.c @EricDavisX

@kpollich
Copy link
Member

kpollich commented Dec 1, 2021

Yes, APM should upgrade automatically when Kibana reboots or the /app/fleet page is loaded again, so that may be a bug. Please confirm by rebooting Kibana or by making a POST /api/fleet/setup API request to Kibana, then verifying the version of APM after setup runs.

The disabled input for "Keep policies up to date" is expected. We made some changes to the logic here in #119126 that added special cases for APM and Synthetics. These integrations ship custom UI's to Kibana with each release, so they require Fleet to upgrade policies so that they'll be compatible with some custom UI's. Therefore, we need to enable this setting and "freeze" it to prevent the user from disabling it. The linked PR description goes into more detail as well.

@EricDavisX
Copy link
Contributor

there is a thread regarding the available version of the APM package in 8.0 - it may be a bug, but it may be just the known feature work happening on that team. I'll fwd you a thread in email.

@amolnater-qasource
Copy link
Author

amolnater-qasource commented Dec 2, 2021

Hi @kpollich
Thanks for sharing the details.

  • On restarting kibana, APM integration upgraded to latest version.

So, should we expect this for now?

@EricDavisX Thanks for sharing the thread, that was helpful.
Further we will keep track of APM integration in future if not upgraded automatically without kibana restart on next snapshot builds.
Thanks

@kpollich
Copy link
Member

So, should we expect this for now?

Yes this should be expected behavior. APM, Endpoint, and Synthetics packages should all exhibit this behavior.

@amolnater-qasource
Copy link
Author

Hi @kpollich
Thanks for confirming the expected behaviour.

We have created 02 testcases for this expectation for Elastic APM and Elastic Synthetics integration in our Ingest Manager test suite at links:
C164187
C164188

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Ticket having question for Dev team Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

4 participants