-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[ES][v2] Copy Jaeger<->OTLP translator from OTEL Contrib #6923
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
Signed-off-by: Manik2708 <[email protected]>
@yurishkuro @mahadzaryab1 Currently I am working on code-coverage for this converter, but before that I wanted to raise this PR to get a validation from your side to check if I am moving in right direction! Please can you give a review over this? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
❌ Your project status has failed because the head coverage (30.05%) is below the target coverage (95.00%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files@@ Coverage Diff @@
## main #6923 +/- ##
===========================================
- Coverage 96.13% 30.05% -66.09%
===========================================
Files 340 178 -162
Lines 19608 10463 -9145
===========================================
- Hits 18851 3145 -15706
- Misses 572 7076 +6504
- Partials 185 242 +57
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Manik2708 <[email protected]>
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.
how did you come up with this code? I strongly recommend copying the code from OTEL and adjusting for the DB model, because the logical transformation is pretty much the same.
I would even say do a PR that is a straight copy (adjusting for package name), with tests and all, and then in the next PR adjust for dbmodel. This way we will see which changes are being applied to the otherwise official transformation. |
Yes, this code is highly inspired from the OTEL code! |
Signed-off-by: Manik2708 <[email protected]>
to_dbmodel
to convert OTEL Traces to DB Spansjaegerproto_to_traces
and traces_to_jaegerproto
to Jaeger
please add tests to ensure 100% coverage, there's no reason for conversion code to be not covered. |
Signed-off-by: Manik2708 <[email protected]>
Signed-off-by: Manik2708 <[email protected]>
Signed-off-by: Manik2708 <[email protected]>
Signed-off-by: Manik2708 <[email protected]>
jaegerproto_to_traces
and traces_to_jaegerproto
to Jaeger…ng#6923) ## Which problem is this PR solving? - Fixes a part of: jaegertracing#6458 ## Description of the changes - Implement the conversion of OTEL Traces to DB Spans as a first step for implementing v2 writer ## How was this change tested? - Not tested yet ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: Manik2708 <[email protected]>
…ng#6923) ## Which problem is this PR solving? - Fixes a part of: jaegertracing#6458 ## Description of the changes - Implement the conversion of OTEL Traces to DB Spans as a first step for implementing v2 writer ## How was this change tested? - Not tested yet ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: Manik2708 <[email protected]> Signed-off-by: amol-verma-allen <[email protected]>
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:npm run lint
andnpm run test