[Fleet] Add OpAMP mappings for UI search#261957
Merged
juliaElastic merged 2 commits intoelastic:mainfrom Apr 9, 2026
Merged
Conversation
Contributor
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]Page load bundle
History |
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
ApprovabilityVerdict: Needs human review This PR adds new Elasticsearch field mappings for OpAMP search functionality in Fleet. While the changes are purely additive schema definitions, the modified file is owned by @elastic/fleet and the author is not a designated owner. Schema/mapping changes to Fleet's agent index should be reviewed by the owning team. You can customize Macroscope's approvability policy. Learn more. |
jillguyonnet
approved these changes
Apr 9, 2026
Member
jillguyonnet
left a comment
There was a problem hiding this comment.
I'm struggling to run the collector, but I'm sure it's an issue with my config. Code looks good 👍
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
Relates https://github.com/elastic/ingest-dev/issues/7062
Added new mappings in elastic/elasticsearch#145824 to kibana so the UI search works on them.
To verify:
Start ES from source with so the new mappings apply (switch to the branch of the ES PR):
Add a collector (follow steps in elastic/fleet-server#6769) and test that the UI search works on the new fields:
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.