Skip to content
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

Consume new API format #466

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

everett980
Copy link
Collaborator

The payload format has changed slightly, update transformDdgData to handle this change, and update view traces to consume multiple traceIDs per path elem.

Signed-off-by: Everett Ross <reverett@uber.com>
@codecov
Copy link

codecov bot commented Oct 14, 2019

Codecov Report

Merging #466 into master will decrease coverage by 0.02%.
The diff coverage is 40%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #466      +/-   ##
==========================================
- Coverage   89.37%   89.35%   -0.03%     
==========================================
  Files         189      189              
  Lines        4424     4434      +10     
  Branches     1061     1063       +2     
==========================================
+ Hits         3954     3962       +8     
- Misses        424      426       +2     
  Partials       46       46
Impacted Files Coverage Δ
...ts/DeepDependencies/Graph/DdgNodeContent/index.tsx 35.29% <0%> (-3.42%) ⬇️
...kages/jaeger-ui/src/model/ddg/transformDdgData.tsx 100% <100%> (ø) ⬆️
...er-ui/src/model/ddg/sample-paths.test.resources.js 100% <100%> (ø) ⬆️
...eViewer/TimelineHeaderRow/TimelineViewingLayer.tsx 91.52% <0%> (-1.7%) ⬇️
packages/jaeger-ui/src/utils/date.tsx 90.47% <0%> (+4.76%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c5eaca5...8efe8ec. Read the comment docs.

Signed-off-by: Everett Ross <reverett@uber.com>
Comment on lines +193 to +196
{
key: 'exemplar_trace_id',
value: `trace ${i} a`,
},
Copy link
Contributor

Choose a reason for hiding this comment

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

@yurishkuro I don't recall our previous discussion - but is there a particular reason to prefer this to combining multivalued keys in the backend as so?

{ 
key: 'exemplar_trace_id',
values: {'traceId1', 'traceId2`, ...}
}

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Additionally, is there a reason to prefer the above implementation or the live implementation over:

attributes: {
  exemplar_trace_id: ['traceID1', 'traceID2', ...],
  [someOtherKey]: ['value0', 'value1'],
},

@everett980 everett980 merged commit 98530d6 into jaegertracing:master Oct 15, 2019
vvvprabhakar pushed a commit to vvvprabhakar/jaeger-ui that referenced this pull request Jul 5, 2021
…ad-format

Consume new API format
Signed-off-by: vvvprabhakar <vvvprabhakar@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants