[Enhancement]: 'upgrade available' Tooltip requirement for lower packages version on Policies detail tab.

[dikshachauhan-qasource]

Describe the feature:
'upgrade available' Tooltip is required for lower packages version on Policies detail tab against integrations that are out-of-date and can be updated to latest available package.

Describe a specific use case for the feature:
We are suggesting this because there might be very limited chances of user visiting to Settings tab of any installed integration. And as currently, this feature is available on integrations settings tab only.

So lets suppose, user is using a package Apache and when he installed this, it was at version say 2.3, however a new package was available with more features to trace on. But user is unaware of new package being available until he visits Integrations settings tab.

Considering that probability of referring policies with greater frequency, we would like to suggest to provided 'upgrade available' Tooltip for lower packages version on Policies detail tab.

Screenshot:

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[manishgupta-qasource]

Reviewed and assigned to @EricDavisX

[EricDavisX]

@ph @jen-huang fyi, not sure how we prefer to process known Enhs from the team. @mostlyjason fyi.

[mostlyjason]

I think this is a great idea. I believe we've had support issues caused by an out of date version. This would improve visibility of it.

CC @hbharding for UX input

[hbharding]

I agree this would help. Though, I think we can do better than simply providing an indicator + tooltip that says "update available" on the agent policy page. At the very least, there should be instruction in the tooltip so users know how to update the package. Even better, we could provide a link to the Integration's settings page or possibly a button inside the tooltip to perform the action without having to leave the current page.

[EricDavisX]

Henry's ideas are exciting, I like them much. :) I do want to encourage progress over perfection though.

...if scope creep keeps it from being enhanced it doesn't help users. The reason I mention is because of the complexities raised in #92612 about package upgrading in general (it is more complex than at may first seem)

[hbharding]

I hear you @EricDavisX. Definitely don't mean to say we should do everything I described, just wanted to through some ideas out there for the record :). The "easy mode button" I described is definitely beyond the scope of what we should do as a first step.

The problem we're trying to solve is providing visibility to users for when a configured integration is not using the latest package version. There's an easy solution for that, but thinking 1 step further from a user perspective, i.e. "what am I supposed to do with this information", ideally there should be some indication for how to resolve it. Users may not know where to find the "update to latest version" button, especially in the future when Integrations will be separate from Fleet. Here's how we could address this now:

If an integration is not using the latest package version, add a yellow "alert" icon indicator + hover tooltip next to the integration version on both the Agent policy detail view and Integration detail's policies tab. The tooltip could say:

Title: Update available
Text: Go to the integration's setting tab to update to the latest version

We should also use the same tooltip here:

Side Note: I'm using the word "update" rather than "upgrade" to be consistent with how we refer to this today in the UI. I've noticed most of our issues refer to this as "upgrade". At the same time, this is inconsistent with Fleet where users can "Upgrade the agent binary version" but with Integrations, we have "Update to the latest version". Happy to open an issue for this if others agree these should align.

Screenshots where say "updates"

---

... After typing all this up, I just discovered this has already been discussed here #93712. @jen-huang opted not to show this information due to performance concerns. #90308 (comment) Is there anything we can do about that?

[EricDavisX]

Thank you @hbharding - the ideas are all great, and I'm glad we're on the same page so far. Just wanted to re-highlight, the button click for 'updating' the Package is just the first step in the process of switching out or creating new Integration policies and applying them to the Agents. It is a minimally cumbersome step, but the biggest concern, people don't know they need to do it.

[EricDavisX]

do we want to target anything specific for 7.13? just confirming / scope and intention.

[jlind23]

Closing as not relevant anymore.

[harshitgupta-qasource]

Hi Team,

We have revalidated this issue on latest 8.8.0 SNAPSHOT Kibana cloud environment and found it fixed now.

Observations:

• 'Upgrade available' Tooltip for lower packages version is available on Policies detail tab

Build details:
VERSION: 8.8.0
BUILD: 61938
COMMIT: 1b18bc2

Screen-Shot:

Hence, we are marking this issue as QA:Validated.

Thanks