-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[ES][v2] Implement FindTraces
for ES/OS for v2
#7021
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
TraceReader
for ES/OS for v2
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7021 +/- ##
==========================================
- Coverage 96.04% 96.03% -0.02%
==========================================
Files 355 355
Lines 20973 20987 +14
==========================================
+ Hits 20144 20155 +11
- Misses 624 626 +2
- Partials 205 206 +1
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]>
TraceReader
for ES/OS for v2FindTraces
for ES/OS for v2
/Don't Merge completing the code-coverage |
nit: I changed description to link to #7034, not the parent ticket. |
Signed-off-by: Manik2708 <[email protected]>
Signed-off-by: Manik2708 <[email protected]>
## Which problem is this PR solving? - Fixes a part of: jaegertracing#7034 ## Description of the changes - Implement the `FindTraces` for ES/OS for v2 ## How was this change tested? - Unit Tests ## 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]>
## Which problem is this PR solving? - Fixes a part of: jaegertracing#7034 ## Description of the changes - Implement the `FindTraces` for ES/OS for v2 ## How was this change tested? - Unit Tests ## 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
FindTraces
for ES/OS for v2How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:npm run lint
andnpm run test