[Fleet] Agent activity

[juliaElastic]

Summary

Resolves #140267

Added agent activity flyout following the new design.

• Agent activity button on agent list page, next to Add agent buttons.
• Flyout showing In progress and completed actions in descending time order.
• Upgrade callout and abort moved to flyout
• Added tour for first time after action is taken from UI

Pending:

• adding tests
• (Done) update texts everywhere with i18n
• openapi update

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[kpollich]

A few patterns in the code here that I think are worth changing. Haven't gotten a chance to pull down locally and test (will do so tomorrow), but overall things are looking great here. Thanks for putting this together so quickly @juliaElastic!

[nchaulet]

Should we clean somehow the unenroll action when the user force unenroll an agent? (probably a follow up issue)

Here I unenrolled an offline agent, than force unenrolled and the UI is stuck with this

[juliaElastic]

Should we clean somehow the unenroll action when the user force unenroll an agent? (probably a follow up issue)

Here I unenrolled an offline agent, than force unenrolled and the UI is stuck with this

Good point, I think this is an existing issue made visible with the activity flyout. This could be improved by kibana querying any in progress unenroll actions for the agents being force unenrolled, and making them completed. I would take this to a separate issue.

Created: #140794

There is a similar issue with stuck in progress actions in case of validation failures, commented here: #141567

[nchaulet]

Looks good to me 🚀

[juliaElastic]

@kpollich are you ready to approve? I updated the requested changes.

[kpollich]

All comments addressed so LGTM 🚀

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e0055ee

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	719	721	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	869.6KB	879.4KB	+9.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	105.9KB	105.9KB	-3.0B

History

• 💚 Build #72623 succeeded 8bc0266
• 💚 Build #72570 succeeded bb71297
• 💚 Build #72530 succeeded cd41522
• 💚 Build #72235 succeeded 67b4621
• 💔 Build #72161 failed ea7cfbc
• 💔 Build #72136 failed cba25e1

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @juliaElastic

[ghost]

Hi @juliaElastic ,

We have created below 13 test cases for this feature under our Fleet Test Suite:

• [C167989]: Validate that ‘Agent activity history’ pop-up is shown on re-assigning policy, upgrade, and unenrolling agents
• [C167990]: Validate that ‘No activity to display’ text is shown on ‘Agent activity’ flyout when no action is performed on the agent
• [C167991]: Validate that ‘Agent activity’ with clock icon is shown on the Fleet > Agents page
• [C167992]: Validate ‘Agent activity’ flyout gets opened on clicking ‘Agent activity’ link on Fleet > Agents page
• [C167993]: Validate that ‘X agent upgraded’ is shown in green color with a tick sign on ‘Agent activity’ flyout on schedule upgrading ‘X agent’
• [C167994]: Validate that ‘Agent upgrade cancelled’ is shown in gray color with a triangle sign on clicking ‘Abort upgrade’ on ‘Agent activity’ flyout
• [C167995]: Validate that ‘x agent/agents assigned to a new policy’ is shown on ‘Agent activity’ flyout on assigning new policy to the x agent/agents
• [C167996]: Validate that ‘X agent upgraded’ is shown in green color with a tick sign on ‘Agent activity’ flyout on upgrading ‘x agent’
• [C167997]: Validate that ‘x agent/agents force unenrolled’ is shown on ‘Agent activity’ flyout on force unenrolling x agent/agents.
• [C167998]: Validate that the ‘In progress’ section is shown at the top
• [C167999]: Validate that ‘X1 of X agents upgraded’ is shown in red color on ‘Agent activity’ flyout on agents upgrade failure
• [C168000]: Validate that ‘X1 of X agent is assigned to a new policy’ is shown in red color on ‘Agent activity’ flyout on agent not added to new policy
• [C168001]: Validate that ‘x agent/agents unenrolled’ is shown on ‘Agent activity’ flyout on unenrolling x agent/agents

Query

• Could you please confirm when and how many times will 'Agent activity history' pop would be shown as we are getting the pop-up inconsistently many times.

Please review the test cases and let us know if we are missing anything.

Thanks!

[juliaElastic]

@prachigupta-qasource One more scenario can be added: update agent tags will show up now in Agent activity as well: #141376

Could you please confirm when and how many times will 'Agent activity history' pop would be shown as we are getting the pop-up inconsistently many times.

The tour should show up for the first time one of these actions are taken. After that, the tour should be hidden on that cluster (there is a ui setting saved for this).

[ghost]

Hi @juliaElastic ,

Thank you for the update.

We have created below 01 test case for this feature under our Fleet Test Suite:

[C168020]: Validate that ‘X agent/agents updated tags’ is shown on ‘Agent activity’ flyout on updating tags for X agent/agents

Please review the test case and let us know if we are missing anything.

Thanks!

[ghost]

Hi Team,

We have executed 15 testcases for this feature under our Fleet Test run at Fleet 8.5.0-BC2 Feature test plan.

Below are the observations:

• Passed: 13
• Failed: 02 due to bug [Fleet]: No appropriate agent upgrade failed message is available if agents fails to upgrade to the latest version. #140936 and [Fleet]: '1 agent updated tags' is not shown on 'Agent activity' flyout for Updating Tags for one agent  #142557

Build details:

Version: 8.5.0 BC2
Build: 56806
Commit: dc769f45a5a6dafb0a8c8f0c0cabcced4df45e11

Thanks!

[ghost]

Hi @juliaElastic,

As per this issue #144299, we have created 01 test case for this feature under our Fleet Test Suite:

• [C168233]: Validate that ‘1 agent updated settings’ is shown on ‘Agent activity’ flyout on changing the ‘Agent logging level’

Please let us know if anything else is required from our end.

Thanks!