Skip to content

Conversation

@andotorg
Copy link
Contributor

==== 🐛 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 CHANGES log.

@andotorg andotorg changed the title Fix big log4j2 grpc report missing traceId ‘discussions’ #9113 Fix big log4j2 grpc report missing traceId #9113 May 21, 2022
@andotorg andotorg changed the title Fix big log4j2 grpc report missing traceId #9113 Fix big log4j2 grpc report missing traceId May 21, 2022
@andotorg
Copy link
Contributor Author

image

image

* 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
Copy link
Member

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix discussions #9113, log4j2 grpc report missing traceId
* Support `-Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector` in gRPC log report.

Copy link
Member

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.

Copy link
Contributor Author

@andotorg andotorg May 22, 2022

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?

Copy link
Member

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.

Copy link
Contributor Author

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
Copy link
Member

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.

@wu-sheng wu-sheng added enhancement New feature or request plugin labels May 22, 2022
@wu-sheng
Copy link
Member

CI fails, you seem not following code style? Please fix them and adjust them according to the review comments.

@andotorg
Copy link
Contributor Author

CI fails, you seem not following code style? Please fix them and adjust them according to the review comments.

OK, I'll revise it

@andotorg andotorg changed the title Fix big log4j2 grpc report missing traceId Fix bug log4j2 grpc report missing traceId May 22, 2022
@andotorg
Copy link
Contributor Author

#182

@andotorg andotorg closed this May 22, 2022
@wu-sheng
Copy link
Member

Why do you close this and open a new one?

@andotorg
Copy link
Contributor Author

Why do you close this and open a new one?
Change from multiple submissions to one submission, which is relatively concise

@andotorg
Copy link
Contributor Author

Resubmitted, modified according to the specification

@wu-sheng
Copy link
Member

If you want to keep the commit log short, do rebase on your own. Also, we will do squash merge in the final merge.
Keeping in one PR is always better even if the review logs are long because ppl would know the context of our discussion.

This time is fine, next time, please keep in one pull request.

@andotorg
Copy link
Contributor Author

ok, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request plugin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants