[9.2] (backport #11233) Set correct types for otel components in Fleet status #11413
Conversation
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
* Set correct types for otel components in Fleet status * Log a warning if we get a malformed otel component status id * Only sort checkin output in tests * Fix new unit tests (cherry picked from commit 1144501)
mergify
bot
requested review from
swiatekm and
ycombinator
and removed request for
a team
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Contributor
💚 Build Succeeded
cc @swiatekm |
swiatekm
approved these changes
Nov 25, 2025
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.
What does this PR do?
It ensures otel collector component status reported to Fleet has the right component type sets for receivers and exporters. Respectively, we have
exporter -> outputandreceiver -> input.It also does some internal refactoring. The Fleet status translation code was using its own
otelhelperspackage. I moved the contents of that package tootel/translateand made all the status translation code use it, unifying the logic between Fleet status and local status. This improves some of the error messages for local status as a side effect.I've also added unit tests for the Fleet status translation.
Why is it important?
Fleet knows about
inputandoutputcomponent types, so it can now display status for native otel integrations.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testHow to test this PR locally
This is slightly involved, as we don't have any native Otel integrations with actual otel collector configurations.
elastic-package build --zipto generate the integration archive.You should see the integration show up in the UI:
You can also look at the agent document to see the types set in the status.
Related issues
This is an automatic backport of pull request #11233 done by [Mergify](https://mergify.com).