[Fleet] Add collector onboarding steps to UI by juliaElastic · Pull Request #254491 · elastic/kibana

juliaElastic · 2026-02-23T13:28:53Z

Summary

Closes https://github.com/elastic/ingest-dev/issues/7019

To test:

enable feature flag xpack.fleet.enableExperimental: ['enableOpAMP']
Add collector button should be visible on the Fleet UI
When clicking on it, a flyout opens with steps to add collector
The flyout creates an agent policy (id:opamp) and displays opamp config with enrollment api key and fleet server host
The flyout confirms if collectors are connected
The OpAMP policy is hidden from Agent policy list UI

Update: moved the collector button in a context menu with the other add buttons:

add_collector_menu.mov

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

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
If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
Flaky Test Runner was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

See some risk examples
...

elasticmachine · 2026-02-23T16:47:25Z

Pinging @elastic/fleet (Team:Fleet)

nchaulet · 2026-02-23T20:19:37Z

...orm/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/list_page/index.tsx


  // Hide agentless policies by default unless showAgentless toggle is enabled
  const getSearchWithDefaults = (newSearch: string) => {
+    const kueryHideOpAMP = `NOT ${agentPolicySavedObjectType}.name:"${OPAMP_POLICY_NAME}"`;


Why hiding OpAmp agents?

The agents won't be hidden, only the agent policy "OpAMP" because it's not intended to be used for anything else. We could probably show it as a managed policy (so users can't enroll Elastic Agents to it).

nchaulet · 2026-02-23T20:21:02Z

...blic/applications/fleet/sections/agents/agent_list_page/components/search_and_filter_bar.tsx

+                    <EuiToolTip content="Monitor an OTel collector in Fleet with OpAMP.">
+                      <EuiButton
+                        fill
+                        color="accent"


Why the accent color from Eui guideline:

Pulls attention to key indicators like notifications or number of selections

Wanted to use a different color than Add agent, but this is going to change according to https://github.com/elastic/ingest-dev/issues/7019#issuecomment-3948730370

nchaulet · 2026-02-23T20:27:47Z

...ublic/applications/fleet/sections/agents/agent_list_page/components/add_collector_flyout.tsx

+        let opampPolicy = await fetchOpampPolicy();
+        if (!opampPolicy) {
+          // 2. Create if not exists
+          const created = await createOpampPolicyWithHook();


Not totally related to that PR, I have some questions on that:

did we considered creating that policy as part of the setup? I am curious how this will looks like for some that do not use Fleet UI but some IAC tools to add opamp agents.

How that policy will work in non default space should we either have one policy per space, with maybe the space in the id, or should we share that policy accross all spaces and agents at the same time

For IAC tools, they would have to use the API to create/get an enrollment token. We can make it easier for them to create the OpAMP agent policy in setup, so the enrollment token is available with one API call. Alternatively we could document creating a preconfigured OpAMP agent policy for them.

For space support, I think it's a valid use case to group collectors to different spaces, so probably best to create a policy per space, similarly to fleet-server-policy.

For space support, I think it's a valid use case to group collectors to different spaces, so probably best to create a policy per space, similarly to fleet-server-policy.

Should we do this that PR or do we want a followup PR for that? I can create the issue if you want

I can take a look in this PR

nchaulet · 2026-02-23T20:28:11Z

...ublic/applications/fleet/sections/agents/agent_list_page/components/add_collector_flyout.tsx

+    pollImmediately: true,
+  });
+
+  useEffect(() => {


depending on the discussion bellow could be a good candidate for useQuery instead

nimarezainia · 2026-02-24T03:38:55Z

@juliaElastic I made some comments in https://github.com/elastic/ingest-dev/issues/7019 to slightly re-design this page.

nchaulet

code LGTM 🚀

juliaElastic · 2026-02-26T13:51:47Z

...ic/applications/fleet/sections/agents/agent_details_page/components/agent_dashboard_link.tsx


-  const isLogAndMetricsEnabled = agentPolicy?.monitoring_enabled?.length ?? 0 > 0;
+  const isLogAndMetricsEnabled =
+    (agentPolicy?.monitoring_enabled?.length ?? 0) > 0 || agent.type === 'OPAMP';


Fix a small bug where the metrics dashboard link was hidden because the opamp agent policy doesn't have monitoring enabled.

Before:

After:

elasticmachine · 2026-02-26T15:43:16Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 00fde67

Failed CI Steps

Scout: [ platform / streams_app-stateful-classic ] plugin

Test Failures

[job] [logs] Scout: [ platform / streams_app-stateful-classic ] plugin / local-stateful-classic - Stream data processing - creating steps - should handle insufficient privileges gracefully

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`fleet`	1588	1589	+1

Async chunks

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

id	before	after	diff
`fleet`	2.2MB	2.2MB	+6.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`	193.2KB	193.2KB	+14.0B

History

💛 Build #401217 was flaky ce53bc5
💛 Build #400183 was flaky f7e9e31
💛 Build #399436 was flaky c7e2ace
💔 Build #399350 failed 891f1e7
💔 Build #399280 failed ce8524e
💔 Build #399247 failed c61c34c

mdbirnstiehl

One suggestion, but lgtm!

...ublic/applications/fleet/sections/agents/agent_list_page/components/add_collector_flyout.tsx

…/sections/agents/agent_list_page/components/add_collector_flyout.tsx Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>

## Summary Closes elastic/ingest-dev#7019 To test: - enable feature flag `xpack.fleet.enableExperimental: ['enableOpAMP']` - Add collector button should be visible on the Fleet UI - When clicking on it, a flyout opens with steps to add collector - The flyout creates an agent policy (`id:opamp`) and displays opamp config with enrollment api key and fleet server host - The flyout confirms if collectors are connected - The OpAMP policy is hidden from Agent policy list UI Update: moved the collector button in a context menu with the other add buttons: https://github.com/user-attachments/assets/069e4d2b-978e-4041-bf0b-b29ef6ad3582 <img width="1107" height="569" alt="image" src="https://github.com/user-attachments/assets/e48f146e-2ed3-4346-8f54-4725b0260cfb" /> <img width="1114" height="868" alt="image" src="https://github.com/user-attachments/assets/9fdb04fb-99e2-4a26-a544-6f5779f36a79" /> <img width="585" height="834" alt="image" src="https://github.com/user-attachments/assets/e68ae8f5-26ed-4265-a098-71e4dc2768cd" /> <img width="590" height="838" alt="image" src="https://github.com/user-attachments/assets/e46c4ac3-6204-4a71-b3b6-cb4e4875dc2f" /> <img width="1113" height="614" alt="image" src="https://github.com/user-attachments/assets/93a759b3-6416-4855-9e63-e03abfe12be9" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>

## Summary Closes elastic/ingest-dev#7148 Relates #254491 Relates elastic/ingest-dev#6982 Relates #252541 Enable OpAMP feature flag The feature flag enables the `Add collector` button in Fleet UI and the `/effective_config` route that is used from the Agent Details UI if the agent is an OTel collector. <img width="2214" height="1824" alt="image" src="https://github.com/user-attachments/assets/1520a587-8844-43d4-8d92-e93ca09527fe" /> Serverless: <img width="1308" height="723" alt="image" src="https://github.com/user-attachments/assets/79b9b086-b693-4c45-8bdc-c586bbd71dee" /> ## Release note Enables OpenTelemetry (OTel) collector support in Fleet. Users can now add OTel collector agents via a new Add collector button in the Fleet UI. OTel collectors will be visible in Fleet Agent list, with the ability to monitor them (view their Component Health, Effective Config, link to internal telemetry dashboard). The feature is in technical preview. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary Closes elastic/ingest-dev#7148 Relates elastic#254491 Relates elastic/ingest-dev#6982 Relates elastic#252541 Enable OpAMP feature flag The feature flag enables the `Add collector` button in Fleet UI and the `/effective_config` route that is used from the Agent Details UI if the agent is an OTel collector. <img width="2214" height="1824" alt="image" src="https://github.com/user-attachments/assets/1520a587-8844-43d4-8d92-e93ca09527fe" /> Serverless: <img width="1308" height="723" alt="image" src="https://github.com/user-attachments/assets/79b9b086-b693-4c45-8bdc-c586bbd71dee" /> ## Release note Enables OpenTelemetry (OTel) collector support in Fleet. Users can now add OTel collector agents via a new Add collector button in the Fleet UI. OTel collectors will be visible in Fleet Agent list, with the ability to monitor them (view their Component Health, Effective Config, link to internal telemetry dashboard). The feature is in technical preview. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

add collector UI

711369c

juliaElastic added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Feb 23, 2026

juliaElastic and others added 6 commits February 23, 2026 14:29

Merge branch 'main' into add-collector-ui

c61c34c

Changes from make api-docs

eeebf86

filter out opamp policy from Agent policy list UI

270b466

fix i18n

ce8524e

fix i18n

891f1e7

fix api test

6a36bbc

juliaElastic marked this pull request as ready for review February 23, 2026 16:33

juliaElastic requested review from a team as code owners February 23, 2026 16:34

add unit tests

c7e2ace

botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Feb 23, 2026

nchaulet self-requested a review February 23, 2026 20:16

nchaulet reviewed Feb 23, 2026

View reviewed changes

juliaElastic added 4 commits February 24, 2026 15:47

move buttons to context menu

b08c6f1

replace useEffect with useQuery

fe0458c

fixed test

0617232

create opamp policy per space

f7e9e31

juliaElastic requested a review from nchaulet February 24, 2026 16:29

Merge branch 'main' into add-collector-ui

6657e4f

nchaulet approved these changes Feb 25, 2026

View reviewed changes

juliaElastic requested a review from florent-leborgne February 26, 2026 08:24

juliaElastic and others added 2 commits February 26, 2026 09:24

Merge branch 'main' into add-collector-ui

ce53bc5

always show agent dashboard link for opamp collectors

00fde67

juliaElastic commented Feb 26, 2026

View reviewed changes

mdbirnstiehl approved these changes Feb 26, 2026

View reviewed changes

...ublic/applications/fleet/sections/agents/agent_list_page/components/add_collector_flyout.tsx Outdated Show resolved Hide resolved

juliaElastic and others added 2 commits February 27, 2026 09:01

Update x-pack/platform/plugins/shared/fleet/public/applications/fleet…

7b9ff93

…/sections/agents/agent_list_page/components/add_collector_flyout.tsx Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>

Merge branch 'main' into add-collector-ui

06189db

juliaElastic merged commit a98fe45 into elastic:main Feb 27, 2026
16 checks passed

kibanamachine added the v9.4.0 label Feb 27, 2026

juliaElastic mentioned this pull request Apr 1, 2026

[Fleet] enable OpAMP feature flag #260654

Merged

10 tasks

Conversation

juliaElastic commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Checklist

Identify risks

Uh oh!

elasticmachine commented Feb 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nimarezainia commented Feb 24, 2026

Uh oh!

nchaulet left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Feb 26, 2026

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

Module Count

Async chunks

Page load bundle

History

Uh oh!

mdbirnstiehl left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

juliaElastic commented Feb 23, 2026 •

edited

Loading