[Fleet] Display outputs in agent list table and agent details

[criamico]

Closes #192339

Summary

Display two additional columns with Outputs hosts in agent list table and agent details section

• The two columns show monitoring output and the integrations output and link to the output flyout in settings
• Display a badge that show the outputs set per integration introduced by [UII] Support integration-level outputs #189125
• Same info displayed in agent details as well

To achieve this, I added two new endpoints.

1. Endpoint that fetches all the outputs associated with a single agent policy (outputs defined on agent policy or default defined in global settings and if any, outputs per integration)

GET kbn:/api/fleet/agent_policies/<AGENT_POLICY_ID>/outputs

2. Endpoint that fetches the outputs as above, for a defined set of agent policy ids

POST kbn:/api/fleet/agent_policies/outputs
{
  "ids": ["policy_id1", "policy_id2", ...]
}

The reason to pass an array of ids is to ensure that we fetch the info only for the policies displayed in the table at any given moment.

Screenshots

Agent list

Agent details

Checklist

• 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

For maintainers

• This will appear in the Release Notes and follow the guidelines

[criamico]

@elasticmachine merge upstream

[criamico]

@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[jen-huang]

/ci

[jen-huang]

I think this work is not complete yet. With #189125, each integration can set their own output, so I expect the Output for integrations to be the unique sum of all outputs used by the agent policy's integrations, plus the default one set on the agent policy (or global default if unset).

We should be careful about how we retrieve this "deep" association. Perhaps we should either return all outputs used to the agent policy info GET endpoint, or add a separate endpoint specifically to return outputs for a given agent policy ID.

[criamico]

@elasticmachine merge upstream

[criamico]

With #189125, each integration can set their own output

@jen-huang thanks for pointing it out. I previously missed this piece, so I put back the PR to draft to keep working on it

Perhaps we should either return all outputs used to the agent policy info GET endpoint, or add a separate endpoint specifically to return outputs for a given agent policy ID.

I'm currently working on implementing a new endpoint under agent_policies root:

GET agent_policies/{agentPolicyId}/outputs

My idea is to use this endpoint to retrieve only this information instead of adding it under the existing agent policies get.
I have a very basic draft of this endpoint that can be iterated on:

The response in this case is

{
  "item": {
    "monitoring": {
      "output": {
        "name": "default ES - Multipass",
        "id": "fleet-default-output"
      }
    },
    "data": {
      "output": {
        "name": "default ES - Multipass",
        "id": "fleet-default-output"
      },
      "integrations": [
        {
          "pkgName": "nginx-1",
          "id": "0124705c-1dbb-43fb-8ceb-beb3e867e4c2"
        }
      ]
    }
  }
}

But I'm thinking to return also the name for each output under integrations so I don't need to do another query in the UI down the line.

[criamico]

@elasticmachine merge upstream

[criamico]

@elasticmachine merge upstream

[juliaElastic]

LGTM

[criamico]

@elasticmachine merge upstream

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 34d780d

Failed CI Steps

• FTR Configs #17

Test Failures

• [job] [logs] FTR Configs #17 / core route timeouts idle socket should timeout if payload sending has too long of an idle period

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	1213	1214	+1

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	1296	1301	+5

Async chunks

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

id	before	after	diff
fleet	1.7MB	1.7MB	+3.6KB

Page load bundle

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

id	before	after	diff
fleet	171.8KB	172.4KB	+664.0B

Unknown metric groups

API count

id	before	after	diff
fleet	1421	1426	+5

History

• 💛 Build #244187 was flaky ad9bdf9
• 💔 Build #244128 failed fc6f095
• 💔 Build #243493 failed ef78686
• 💔 Build #243415 failed 77e16d2
• 💔 Build #243237 failed cdb247a
• 💛 Build #241795 was flaky b6e8a5e

cc @criamico

[kibanamachine]

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/11462875221

[kibanamachine]

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/11462875155

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts You might need to backport the following PRs to 8.x: - [DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)

Manual backport

To create the backport manually run:

node scripts/backport --pr 195801

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts You might need to backport the following PRs to 8.x: - [DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)

Manual backport

To create the backport manually run:

node scripts/backport --pr 195801

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 195801 locally