-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
Pinging @elastic/fleet (Team:Fleet) |
reviewed and assigned to @kpollich |
Yes, APM should upgrade automatically when Kibana reboots or the 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. |
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. |
Hi @kpollich
So, should we expect this for now? @EricDavisX Thanks for sharing the thread, that was helpful. |
Yes this should be expected behavior. APM, Endpoint, and Synthetics packages should all exhibit this behavior. |
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:
Could please confirm this behaviour as expected and share us update regarding the use case for both the scenarios if expected.
Screenshot:
The text was updated successfully, but these errors were encountered: