[Fleet] enable OpAMP feature flag#260654
Merged
juliaElastic merged 5 commits intoelastic:mainfrom Apr 7, 2026
Merged
Conversation
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
ApprovabilityVerdict: 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. |
mdbirnstiehl
approved these changes
Apr 2, 2026
florent-leborgne
approved these changes
Apr 3, 2026
| summary: Get an agent's effective config | ||
| tags: | ||
| - Elastic Agents | ||
| x-metaTags: |
Member
There was a problem hiding this comment.
I think we may be missing availability information here
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
|
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 collectorbutton in Fleet UI and the/effective_configroute that is used from the Agent Details UI if the agent is an OTel collector.Serverless:

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.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*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.