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
Add scope (if exists) to exported logs #20659
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It's yours @tamir-michaeli ! |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
The solution for this issue is in pr: #20768 waiting for review |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
**Description:** <Describe what has changed.> In cases when an instrumentation library is used to export logs, the scope field is not being copied to the exported logs. With this patch, if the scope field is populated in the original log, the scopeName field in the exported log will contains the name of the scope. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** #20659 **Testing:** Added a test with a scope name. Changed previous tests to send an empty scope name. **Documentation:** Added a note in the readme. --------- Co-authored-by: Alex Boten <alex@boten.ca> Co-authored-by: Antoine Toulme <antoine@toulme.name> Co-authored-by: Alex Boten <aboten@lightstep.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
…emetry#20768) **Description:** <Describe what has changed.> In cases when an instrumentation library is used to export logs, the scope field is not being copied to the exported logs. With this patch, if the scope field is populated in the original log, the scopeName field in the exported log will contains the name of the scope. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** open-telemetry#20659 **Testing:** Added a test with a scope name. Changed previous tests to send an empty scope name. **Documentation:** Added a note in the readme. --------- Co-authored-by: Alex Boten <alex@boten.ca> Co-authored-by: Antoine Toulme <antoine@toulme.name> Co-authored-by: Alex Boten <aboten@lightstep.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
Component(s)
exporter/logzio
Is your feature request related to a problem? Please describe.
When using OpentelemetryAppender for log4j2 with the collector, originating class and package are missing from the logs.
Example when log exported to a file (using fileexporter):
When the log is exported using logzioexporter, the scope copied into the log.
Describe the solution you'd like
Adding a scope to exported logs, if such scope exists.
Describe alternatives you've considered
Transform Processor, but it cannot be used in this case since the scope is in a different context than the log.
Additional context
I will work on this one :)
The text was updated successfully, but these errors were encountered: