[Fleet] Agent activity

[juliaElastic]

Summary

Resolves #140267

on top of #138870

WIP

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
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[juliaElastic]

I didn't find a better way to determine the completion time of an action, other than to query the last timestamp of action results for this action. Maybe we could have a field on the action document itself to record the completion time when the last agent acked the action.

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: aece6e6
• Interpreting CI Failures

Failed CI Steps

• FTR Configs #30
• FTR Configs #30
• Checks
• Check Types

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	719	721	+2

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
fleet	873	876	+3

Async chunks

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

id	before	after	diff
fleet	865.8KB	872.4KB	+6.5KB

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.7KB	106.1KB	+418.0B

Unknown metric groups

API count

id	before	after	diff
fleet	970	973	+3

ESLint disabled in files

id	before	after	diff
apm	14	13	-1
observability	7	6	-1
total			-2

ESLint disabled line counts

id	before	after	diff
apm	80	78	-2
observability	45	44	-1
synthetics	59	53	-6
ux	10	9	-1
total			-10

Total ESLint disabled count

id	before	after	diff
apm	94	91	-3
observability	52	50	-2
synthetics	65	59	-6
ux	13	12	-1
total			-12

History

• 💔 Build #71259 failed 010f2043a24a0a97261afe05e9dd4ead7507f987
• 💔 Build #71178 failed a6495bf
• 💔 Build #70927 failed 072945d

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

cc @juliaElastic