-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enrich otel logs to match beat process logs #7062
Conversation
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request does not have a backport label. Could you fix it @khushijain21? 🙏
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, had two minor questions.
2092dbb
This pull request is now in conflicts. Could you fix it? 🙏
|
|
💛 Build succeeded, but was flaky
Failed CI Steps
History
|
* Add fields to otel logs (cherry picked from commit ca05561) # Conflicts: # go.mod # go.sum
* Add fields to otel logs
) * Enrich otel logs to match beat process logs (#7062)
What does this PR do?
This PR adds
component.*
fields for components run by the OTelManager. For more reasoning check https://github.com/elastic/ingest-dev/issues/5139Checklist
./changelog/fragments
using the changelog toolHow to test this PR locally
Logs from normal mode
Logs from components run by Otel Manager
Some Differences:
log.source
fields in the latter. It is not misleading, but two fields with same key can be confusing to users.Related issues