-
Notifications
You must be signed in to change notification settings - Fork 521
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
TraceSpanTable View #772
Closed
Closed
TraceSpanTable View #772
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vvvprabhakar
requested review from
everett980,
rubenvp8510 and
tiffon
as code owners
June 23, 2021 11:45
Signed-off-by: Gary Brown <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Gary Brown <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
(cherry picked from commit 3fe952ab8c829072c4e6cd314bfd656c1d1ebfe5) Signed-off-by: Ivan Kopeykin <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Everett Ross <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* Added view for showing detailed trace statistics * Reworked trace statistics ui * review included * feedback added Signed-off-by: Philip Dengler <[email protected]> * Handle merge conflict, clean up AltViewOptions style Signed-off-by: Everett Ross <[email protected]> Co-authored-by: Philip <[email protected]> Co-authored-by: Everett Ross <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
…ertracing#610) Following the react migration path laid out here https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* add unit coverage for component TraceIDSearchInput Signed-off-by: Tim Klever <[email protected]> * Correct copyright holder Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: Tim Klever <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
…cing#615) These tests, due to missing required props, were leaving console.error messages in the test run CLI output. It doesn't effect the tests, it doesn't cause any false positives or negatives, but it could be seen as a distraction seeing red output fly across the screen in an otherwise passing test. Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
…aegertracing#612) Migrating these componentWillRecieveProps calls to componentDidUpdate in line with recommendations provided at https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops, stating "If you need to perform a side effect (for example, data fetching or an animation) in response to a change in props, use componentDidUpdate" Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
…tracing#614) Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Refactor components to no longer use UNSAFE_componentWillMount methods adhering to current React best practices. Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* add test to ensure canvas graph rendering is limited This test codifies the sentiments on SpanGraph/index.tsx#L35, confirming that canvas graph is not re-rendered unless trace is changed Signed-off-by: Tim Klever <[email protected]> * refactor SpanGraph to not use internal state for memoization Using component state in this manner is considered a react anti-pattern. By removing it, not only is the size and complexity of the component reduced, but it enables the removal of the legacy method UNSAFE_componentWillReceiveProps Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* adding test coverage around current ArchiveNotifier component functionality Signed-off-by: Tim Klever <[email protected]> * clean up some outdated comments and remove some erroneous logic Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Per vote here jaegertracing#621 Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* add additional tests around existing TimelineViewingLayer functionality In addition to rounding out the test suite, this commit also removes some of the "Math.random" calls from the test suite. These randoms were causing some code coverage jitter in the test suite by randomly executing certain code paths. Removing these randomizations will keep coverage reporting consistent and avoid random "coverage losses" based on chance. Signed-off-by: Tim Klever <[email protected]> * migrate from callback ref to CreateRef in TimelineViewingLayer CreateRef API was introduced in React 16.3 Signed-off-by: Tim Klever <[email protected]> Co-authored-by: Ruben Vargas Palma <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Gary Brown <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* Fixes TraceTimelineViewer span details Signed-off-by: Ruben Vargas <[email protected]> * perform deep comparision for memoized ViewBoundsFunc and GetCssClasses Signed-off-by: Ruben Vargas <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Bumps [http-proxy](https://github.com/http-party/node-http-proxy) from 1.17.0 to 1.18.1. - [Release notes](https://github.com/http-party/node-http-proxy/releases) - [Changelog](https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md) - [Commits](http-party/node-http-proxy@1.17.0...1.18.1) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Ruben Vargas <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Tim Klever <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Ruben Vargas <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
* feat: upgrade to react-router-dom v5.2.0 Signed-off-by: Meenal Trivedi <[email protected]> * fix: lint Signed-off-by: Meenal Trivedi <[email protected]> * fix Signed-off-by: Meenal Trivedi <[email protected]> * update snapshots to accomodate latest changes Signed-off-by: Meenal Trivedi <[email protected]> * fix Signed-off-by: Meenal Trivedi <[email protected]> * fix: object only has getter Signed-off-by: Meenal Trivedi <[email protected]> * fix: tests Signed-off-by: Meenal Trivedi <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Bumps [memoize-one](https://github.com/alexreardon/memoize-one) from 5.0.0 to 5.1.1. - [Release notes](https://github.com/alexreardon/memoize-one/releases) - [Commits](alexreardon/memoize-one@v5.0.0...v5.1.1) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
This reverts commit 1e43500. Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
* Update jest to produce a junit report for tests Signed-off-by: Kevin Earls <[email protected]> * Fix formatting to make yarn lint happy Signed-off-by: Kevin Earls <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Meenal Trivedi <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
…acing#724) * feat: redesign the search box for jaeger-ui Signed-off-by: Meenal Trivedi <[email protected]> * chore: remove comments Signed-off-by: Meenal Trivedi <[email protected]> * design button Signed-off-by: Meenal Trivedi <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
* feat: upgrade to react-router-dom v5.2.0 Signed-off-by: Meenal Trivedi <[email protected]> * fix: lint Signed-off-by: Meenal Trivedi <[email protected]> * fix Signed-off-by: Meenal Trivedi <[email protected]> * update snapshots to accomodate latest changes Signed-off-by: Meenal Trivedi <[email protected]> * fix Signed-off-by: Meenal Trivedi <[email protected]> * fix: object only has getter Signed-off-by: Meenal Trivedi <[email protected]> * fix: tests Signed-off-by: Meenal Trivedi <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Bumps [cytoscape-dagre](https://github.com/cytoscape/cytoscape.js-dagre) from 2.2.2 to 2.3.2. - [Release notes](https://github.com/cytoscape/cytoscape.js-dagre/releases) - [Commits](cytoscape/cytoscape.js-dagre@v2.2.2...v2.3.2) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: vvvprabhakar <[email protected]>
Bumps [@babel/cli](https://github.com/babel/babel/tree/HEAD/packages/babel-cli) from 7.2.3 to 7.13.14. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.13.14/packages/babel-cli) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: vvvprabhakar <[email protected]>
Bumps [memoize-one](https://github.com/alexreardon/memoize-one) from 5.0.0 to 5.1.1. - [Release notes](https://github.com/alexreardon/memoize-one/releases) - [Commits](alexreardon/memoize-one@v5.0.0...v5.1.1) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why trace span table? Issue(#690)
A trace with many spans trace (~20K) spans can be broken down into pieces and analyzed. Have a link with
traceTimeline View
as well to link both views and get the analysis of traceGives a detailed view of a service or an operation and its impact on a trace,
What can we achieve?
Filter Spans with multiple serviceName values
Filter Spans with multiple OperationName values
Filter with both ServiceName and OperationName
Sort based on duration and startTime
Each row in the table has spanID link which will take the user to that particular span in
traceTimelineView
Either search with text on serviceName and OperatioName Columns
Pagination for the spans
What can we improve from here?
Dependieces Used
Used antd for table
Used react-highlighter for the search word highlighting
**
**