[Fleet] OpAMP UI changes by juliaElastic · Pull Request #252541 · elastic/kibana

juliaElastic · 2026-02-10T13:41:22Z

Summary

Relates https://github.com/elastic/ingest-dev/issues/6829
Closes https://github.com/elastic/ingest-dev/issues/6982

Depends on elastic/fleet-server#6330
Follow the instructions in the fleet-server PR to start an otel collector with OpAMP config.

OTel Collector displayed in Fleet UI including:

Capabilities
Component Health
Effective Config (click on View Collector Configuration)
Link to OTel internal dashboard (click on View more agent metrics) https://github.com/elastic/opentelemetry-dev/issues/1038
Calculate CPU and Memory metrics from internal telemetry for OTel collectors

Added .fleet-agents mappings for the new fields to be searchable (e.g. identifying attributes): elastic/elasticsearch#142550

OpAMP_UI.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
...

juliaElastic · 2026-02-13T14:44:17Z

x-pack/platform/plugins/shared/fleet/server/services/agents/helpers.ts

+    sequence_num: hit._source?.sequence_num,
+    capabilities: hit._source?.capabilities,
+    health: hit._source?.health,
+    effective_config: hit._source?.effective_config,


Alternatively we could omit effective_config from here (to be returned in the /agents API) and have a separate API call to return effective_config only when View Collector Configuration is clicked.
This would reduce the size of /agents` API responses, as effective config can be quite large.

Decided to move out effective_config to another API, as we call the /agents API many times, so it's better to query effective_config only when the button is clicked.

cfe3d1e

juliaElastic · 2026-02-17T08:25:45Z

x-pack/platform/plugins/shared/fleet/common/constants/mappings.ts

Tested searching on identifying attributes on the UI:

florent-leborgne

LGTM for docs; 2 minor suggestions that you can feel free to ignore on the copy

...ctions/agents/agent_details_page/components/agent_details/agent_details_component_health.tsx

...ations/fleet/sections/agents/agent_details_page/components/agent_effective_config_flyout.tsx

elasticmachine · 2026-02-17T18:07:33Z

Pinging @elastic/fleet (Team:Fleet)

nchaulet

I did a first code only pass, looks good

nchaulet · 2026-02-17T17:31:12Z

x-pack/platform/plugins/shared/fleet/server/services/agents/crud.ts


 export function removeSOAttributes(kuery: string) {
-  return kuery.replace(/attributes\./g, '').replace(/fleet-agents\./g, '');
+  return kuery.replace(/\.attributes\./g, '').replace(/fleet-agents\./g, '');


nit: it will be great to add a unit test for that with the property that was breaking, it will serve as documentation and avoid we break it later

added unit tests

nchaulet · 2026-02-17T19:11:30Z

x-pack/platform/plugins/shared/fleet/server/services/agents/agent_metrics.ts

+    fleetAgents = await _fetchAndAssignAgentMetrics(esClient, fleetAgents);
+    opampAgents = await _fetchAndAssignOtelMetrics(esClient, opampAgents);
+    return [...fleetAgents, ...opampAgents];


In case where we have mixed fleetAgent and opampAgents this could messed up the order now?

refactored to keep the agent order

nchaulet · 2026-02-17T19:27:04Z

...ctions/agents/agent_details_page/components/agent_details/agent_details_component_health.tsx

+  });
+};
+
+export const AgentDetailsComponentHealth: React.FunctionComponent<{


Nit: if that component is only used for opamp maybe have some distinctive naming

good point, renamed

nchaulet · 2026-02-17T19:29:07Z

x-pack/platform/plugins/shared/fleet/server/routes/agent/handlers.ts

+  const esClient = appContextService.getInternalUserESClient();
+  const agentDoc = await esClient.get({
+    index: AGENTS_INDEX,
+    id: request.params.agentId,


I guess opamp agent could belong to different space depending of the policy space, we may need a check that agent belong to the current space here (maybe just retrieving the agent will do the trick)

added verification for current space

…/sections/agents/agent_details_page/components/agent_details/agent_details_component_health.tsx Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>

…/sections/agents/agent_details_page/components/agent_effective_config_flyout.tsx Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>

nchaulet

LGTM 🚀

juliaElastic · 2026-02-18T14:36:02Z

...shared/fleet/public/applications/fleet/sections/agents/hooks/use_single_agent_menu_items.tsx

Added a change to hide most actions for OpAMP agents:

Single agent action list has View agent JSON:

Bulk agent action list has Export to CSV:

Hiding actions in case of a mixed selection, because otel collectors wouldn't be handled correctly if included in a bulk action.

elasticmachine · 2026-02-18T14:46:27Z

⏳ Build in-progress, with failures

Buildkite Build
Commit: b388eca

Failed CI Steps

Test Failures

[job] [logs] FTR Configs #152 / console app console autocomplete feature Autocomplete shouldnt trigger within a multiline block comment

History

juliaElastic · 2026-02-19T08:45:38Z

x-pack/platform/plugins/shared/fleet/public/components/agent_policy_summary_line.tsx

    const isOutdated = agent?.policy_revision && policy.revision > agent.policy_revision;

+    if (agent?.type === 'OPAMP') {
+      return <EuiText>-</EuiText>;


Hide agent policy name, so it's not misleading.

## Summary Relates elastic/ingest-dev#6829 Closes elastic/ingest-dev#6982 Depends on elastic/fleet-server#6330 Follow the instructions in the fleet-server PR to start an otel collector with OpAMP config. OTel Collector displayed in Fleet UI including: - Capabilities - Component Health - Effective Config (click on View Collector Configuration) - Link to OTel internal dashboard (click on View more agent metrics) elastic/opentelemetry-dev#1038 - Calculate CPU and Memory metrics from internal telemetry for OTel collectors Added `.fleet-agents` mappings for the new fields to be searchable (e.g. identifying attributes): elastic/elasticsearch#142550 https://github.com/user-attachments/assets/a0a30e31-c7cd-456b-9004-4002c36c46fe <img width="1245" height="864" alt="image" src="https://github.com/user-attachments/assets/8c092c76-a789-4ddb-8265-3191268cfb80" /> <img width="1249" height="861" alt="image" src="https://github.com/user-attachments/assets/ae9e0835-cbe4-4ed5-b3ab-d0720d8775e8" /> <img width="1802" height="623" alt="image" src="https://github.com/user-attachments/assets/0256693f-6da9-457a-a363-1d8e54d94973" /> <img width="1245" height="852" alt="image" src="https://github.com/user-attachments/assets/d1cec06f-9116-40cc-ba65-da42e16b6f12" /> <img width="1752" height="626" alt="image" src="https://github.com/user-attachments/assets/d190065a-b4be-4682-b1ff-6314a4ada9c8" /> ### 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: florent-leborgne <florent.leborgne@elastic.co>

## 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>

opamp UI changes

4deedd4

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

kibanamachine and others added 5 commits February 10, 2026 14:01

Changes from make api-docs

845f2c3

fix checks

7761575

fix checks

0a222f9

use internal telemetry

3ce17f4

update component health labels

120e669

juliaElastic commented Feb 13, 2026

View reviewed changes

juliaElastic and others added 13 commits February 13, 2026 15:45

add tests

fab1a37

fix checks

520760d

Merge branch 'main' into opamp

d55ebd3

add API to query effective config

cfe3d1e

Changes from make api-docs

424efbf

fix oas validation errors

6219fe9

remove effective_config from searchHitToAgent

d607c34

Changes from make api-docs

aa207f0

add integration test

5f5ed35

wrap capabilities + mappings

e56a2b0

attributes mappings

0dfb583

Merge branch 'main' into opamp

0990a81

fix replacing attributes

76eed63

juliaElastic commented Feb 17, 2026

View reviewed changes

juliaElastic and others added 3 commits February 17, 2026 10:31

fix tests

20ae79e

Merge branch 'main' into opamp

5d1a677

hide outdated policy for opamp

df8e140

juliaElastic marked this pull request as ready for review February 17, 2026 14:34

juliaElastic requested review from a team as code owners February 17, 2026 14:34

nchaulet self-requested a review February 17, 2026 16:17

florent-leborgne approved these changes Feb 17, 2026

View reviewed changes

...ctions/agents/agent_details_page/components/agent_details/agent_details_component_health.tsx Outdated Show resolved Hide resolved

...ations/fleet/sections/agents/agent_details_page/components/agent_effective_config_flyout.tsx Outdated Show resolved Hide resolved

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

nchaulet reviewed Feb 17, 2026

View reviewed changes

juliaElastic and others added 5 commits February 18, 2026 09:16

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

fb346f6

…/sections/agents/agent_details_page/components/agent_details/agent_details_component_health.tsx Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>

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

ce35ce7

…/sections/agents/agent_details_page/components/agent_effective_config_flyout.tsx Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>

address review comments

1c82c6c

fix unit test

3d4dd41

keep order of agents when fetching metrics

fcfc406

juliaElastic requested a review from nchaulet February 18, 2026 12:45

juliaElastic added 2 commits February 18, 2026 13:52

add mappings for passthrough fields

63e0e1a

fix unit test

fd78d1d

nchaulet approved these changes Feb 18, 2026

View reviewed changes

hide most actions for opamp agents

b388eca

juliaElastic commented Feb 18, 2026

View reviewed changes

hide agent policy name for opamp type

88001ff

juliaElastic commented Feb 19, 2026

View reviewed changes

juliaElastic merged commit 1a28691 into elastic:main Feb 19, 2026
16 checks passed

kibanamachine added the v9.4.0 label Feb 19, 2026

juliaElastic mentioned this pull request Apr 1, 2026

[Fleet] enable OpAMP feature flag #260654

Merged

10 tasks

Conversation

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

Uh oh!

Summary

Checklist

Identify risks

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!

florent-leborgne left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

elasticmachine commented Feb 17, 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!

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!

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 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⏳ Build in-progress, with failures

Failed CI Steps

Test Failures

History

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

juliaElastic commented Feb 10, 2026 •

edited

Loading

elasticmachine commented Feb 18, 2026 •

edited

Loading