Skip to content

[Fleet] enable OpAMP feature flag#260654

Merged
juliaElastic merged 5 commits intoelastic:mainfrom
juliaElastic:enable-opamp
Apr 7, 2026
Merged

[Fleet] enable OpAMP feature flag#260654
juliaElastic merged 5 commits intoelastic:mainfrom
juliaElastic:enable-opamp

Conversation

@juliaElastic
Copy link
Copy Markdown
Contributor

@juliaElastic juliaElastic commented Apr 1, 2026

Summary

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

Relates #254491
Relates https://github.com/elastic/ingest-dev/issues/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.

image

Serverless:
image

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

@juliaElastic juliaElastic added backport:skip This PR does not require backporting release_note:feature Makes this part of the condensed release notes v9.4.0 labels Apr 1, 2026
@juliaElastic juliaElastic marked this pull request as ready for review April 2, 2026 08:27
@juliaElastic juliaElastic requested review from a team as code owners April 2, 2026 08:27
Copy link
Copy Markdown
Member

@jillguyonnet jillguyonnet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM!

@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Apr 2, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/fleet (Team:Fleet)

@macroscopeapp
Copy link
Copy Markdown
Contributor

macroscopeapp bot commented Apr 2, 2026

Approvability

Verdict: Needs human review

This PR enables the OpAMP feature flag, activating a new API endpoint and UI changes that were previously gated. Feature flag enablement that introduces new user-facing capabilities warrants review by the @elastic/fleet team who owns these files.

You can customize Macroscope's approvability policy. Learn more.

summary: Get an agent's effective config
tags:
- Elastic Agents
x-metaTags:
Copy link
Copy Markdown
Member

@florent-leborgne florent-leborgne Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may be missing availability information here

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #2 / Endpoint plugin @ess @serverless @skipInServerlessMKI Endpoint Scripts Library RBAC Get one API "before each" hook for "should return script when user has READ privileges"

Metrics [docs]

✅ unchanged

History

@juliaElastic juliaElastic merged commit e2eaae3 into elastic:main Apr 7, 2026
18 checks passed
@juliaElastic juliaElastic added the ci:project-deploy-observability Create an Observability project label Apr 7, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@juliaElastic juliaElastic removed the ci:project-deploy-observability Create an Observability project label Apr 7, 2026
kelvtanv pushed a commit to kelvtanv/kibana that referenced this pull request Apr 7, 2026
## 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:feature Makes this part of the condensed release notes Team:Fleet Team label for Observability Data Collection Fleet team v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants