[WIP][UII] Add status tracking for agentless integrations

[jen-huang]

Summary

Resolves https://github.com/elastic/ingest-dev/issues/3933. For deployments that support agentless, integrations with agentless deployment mode enabled will allow the status of agentless integration policies to be tracked.

Key technical changes

• A new field supports_agentless was added to package policies. This field also exists on agent policies. When an agentless integration is created, supports_agentless: true is now added to both the package policy and its parent agent policy.
  • This allows easier filtering for agentless integrations as we avoid having to retrieve & check against every parent agent policy.
  • This also means existing agentless policies do not get this new status tracking UI, only new ones created after this change. Since agentless is not yet GA, I think this is okay.
• /api/fleet/agent_status/data now takes an optional query param pkgKey. When pkgKey is specified, the API will check if agent(s) have ingested data for only that package's datastreams.

UI walkthrough

Click to show

1. **Integration policies** page now shows two tables for integrations meeting the above condition, one for agentless policies and one for agent-based policies:  2. Clicking the status badge in the agentless policies table opens a flyout with two steps: confirm agentless enrollment and confirm incoming data:  3. Confirm agentless enrollment polls for an agent enrolled into that integration policy's agent policy. If that agent is reporting an unhealthy status, the integration component UI is shown. This UI is the same one used on Fleet > Agents > Agent details page and shows all components reported by that agent:  4. Once a healthy agentless enrollment is established, confirm incoming data starts polling for data for that integration ingested by that agent ID in the past 5 minutes:  5. If data could not be retrieved in 5 minutes, an error message shows while polling continues in the background:  6. If data is retrieved, a success message is shown: 

To-do

• [ ] API tests
• [ ] Unit UI tests
• [ ] Manual Cloud tests
• [ ] File docs request
  • [ ] Update troubleshooting guide link

Checklist

Delete any items that are not applicable to this PR.

• [x] 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]

:robot: Jobs for this PR can be triggered through checkboxes. :construction: :information_source: To trigger the CI, please tick the checkbox below :point_down: - [ ] Click to trigger **kibana-pull-request** for this PR! - [ ] Click to trigger **kibana-deploy-project-from-pr** for this PR!

[elasticmachine]

:broken_heart: Build Failed

• Buildkite Build
• Commit: 71267fb69586b75e2782cfdf692edd702297f3a7

Failed CI Steps

• Checks
• Check OAS Snapshot

History

• :broken_heart: Build #249761 failed 3145f50e0a6efbca293f4f51310f50a3a563812d

cc @jen-huang