-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
feat(apm): Navigate from an ancestor transaction to a descendent transaction within a trace #15926
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
fbe97d2 to
0ec0e0e
Compare
d31d129 to
e5a78e7
Compare
970cd07 to
ce938ff
Compare
c125293 to
d58628e
Compare
…saction within a trace
d58628e to
2e2802d
Compare
| if ( | ||
| !response.data || | ||
| !Array.isArray(response.data) || | ||
| response.data.length <= 0 |
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.
Would length be less than 0?
| }); | ||
| } | ||
|
|
||
| fetchSpanDescendents(spanID: string): Promise<any> { |
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.
Could move this into an actioncreator module. Having components doing both request/response handing and rendering DOM gets hard to maintain.
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'll do this in a follow up PR.
NOTES
TODO
trace.parent_spanquery feat(discover2) Add public fields to discover for tracing #15959feasible solution for child to parent traversalEDIT: not feasible