-
Notifications
You must be signed in to change notification settings - Fork 477
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
Consume new API format #466
Conversation
Signed-off-by: Everett Ross <reverett@uber.com>
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
Signed-off-by: Everett Ross <reverett@uber.com>
{ | ||
key: 'exemplar_trace_id', | ||
value: `trace ${i} a`, | ||
}, |
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.
@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`, ...}
}
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.
Additionally, is there a reason to prefer the above implementation or the live implementation over:
attributes: {
exemplar_trace_id: ['traceID1', 'traceID2', ...],
[someOtherKey]: ['value0', 'value1'],
},
…ad-format Consume new API format Signed-off-by: vvvprabhakar <vvvprabhakar@gmail.com>
The payload format has changed slightly, update
transformDdgData
to handle this change, and update view traces to consume multiple traceIDs per path elem.