Skip to content

Tracer should trace exception to DefaultNode #1066

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.

Sign up for GitHub

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

Jump to bottom
Closed
joooohnli opened this issue Sep 24, 2019 · 0 comments · Fixed by #1068
Closed

Tracer should trace exception to DefaultNode #1066

joooohnli opened this issue Sep 24, 2019 · 0 comments · Fixed by #1068
Labels
kind/question Category issues related to questions or problems

Comments

@joooohnli
Copy link
Contributor

Issue Description

bug report

Describe what happened (or what feature you want)

Tracer only trace exception to ClusterNode

Describe what you expected to happen

Tracer should trace exception to both DefaultNode and ClusterNode

How to reproduce it (as minimally and precisely as possible)

com.alibaba.csp.sentinel.Tracer#traceExceptionToNode
image

Tell us your environment

1.6.3

Anything else we need to know?
@sczyh30 sczyh30 added the kind/question Category issues related to questions or problems label Sep 27, 2019
@joooohnli joooohnli mentioned this issue Sep 27, 2019
Merged
CST11021 pushed a commit to CST11021/Sentinel that referenced this issue Nov 3, 2021
@caojiele @zongtanghu
[RIP-9](Operation) within deleted title(alibaba#1066)
a1d4ce0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question Category issues related to questions or problems
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Tracer does not trace exception to DefaultNode joooohnli/Sentinel
2 participants
@joooohnli @sczyh30