-
Notifications
You must be signed in to change notification settings - Fork 669
Fix bug log4j2 grpc report missing traceId #181
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
Conversation
| * Enhance Apache ShenYu (incubating) plugin: support trace `grpc`,`sofarpc`,`motan`,`tars` rpc proxy. | ||
| * Add primary endpoint name to log events. | ||
| * Fix Span not finished in gateway plugin when the gateway request timeout. | ||
| * Fix discussions #9113, log4j2 grpc report missing traceId |
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.
I think we need some update on the docs https://skywalking.apache.org/docs/skywalking-java/latest/en/setup/service-agent/java-agent/application-toolkit-log4j-2.x/
Please update application-toolkit-log4j-2.x.md accordingly.
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.
| * Fix discussions #9113, log4j2 grpc report missing traceId | |
| * Support `-Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector` in gRPC log report. |
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.
Notice #9113 is actually not working, because this is not in the same repository.
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.
Do I need to recreate an issues?
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.
No, I mean the link.#issue/discussion number is only working as a link when PR and issue are in the same repo. And we don't put this in the change log. The changelog is related to a commit/PR already.
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.
ok
| .setSpanId(ContextManager.getSpanId()) | ||
| .setTraceSegmentId(ContextManager.getSegmentId()) | ||
| .build()).build(); | ||
| // fix -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector not traceId |
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.
This comment seems not current. You should explain about AsyncLoggerContextSelector is working on async mode, so it has to use SkyWalkingContext.
Comments for fix xxx actually is pointless, because git log already includes this information.
|
CI fails, you seem not following code style? Please fix them and adjust them according to the review comments. |
OK, I'll revise it |
|
Why do you close this and open a new one? |
|
|
Resubmitted, modified according to the specification |
|
If you want to keep the commit log short, do This time is fine, next time, please keep in one pull request. |
|
ok, thanks |


==== 🐛 Remove this line WHEN AND ONLY WHEN you're fixing a bug, follow the checklist 👇 ====
Fix apache/skywalking#9113
[✅] Fix the problem that traceid cannot be reported when log4j2 global is modified to asynchronous log
==== 🐛 Remove this line WHEN AND ONLY WHEN you're fixing a bug, follow the checklist 👆 ====
[✅] Update the
CHANGESlog.