feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873

sAchin-680 · 2025-03-18T21:02:47Z

This pull request introduces an example configuration for Jaeger Query v2 as part of the effort to improve compatibility with the OpenTelemetry (OTEL) Collector architecture.

Key Changes:

Imported the nop receiver and exporter to define a minimal pipeline.
Created a sample query service configuration that excludes the ingestion pipeline.
Extended E2E integration tests to validate the new configuration.
Updated the CI workflow (ci-crossdock.yml) to support Jaeger Query v2 testing.
Enhanced documentation to guide users on the setup and usage.

Which problem is this PR solving?

Jaeger Query operates as a read-only service and does not require an ingestion pipeline. However, due to OTEL Collector’s architecture, a minimal pipeline is necessary. To work around this, the nop receiver and nop exporter are introduced as a placeholder pipeline.

This approach aligns with ongoing discussions:

Jaeger Query v2 Discussion
Related OTEL Collector issue: open-telemetry/opentelemetry-collector#12613

Description of the changes

Changes Introduced

Imported OTEL Collector’s nop receiver and nop exporter to enable a minimal pipeline.
Added config-query.yml: A dedicated configuration file for Jaeger Query v2.
Updated CI tests (ci-crossdock.yml) to verify Query v2 functionality.
Extended E2E test coverage to validate the correctness of the new configuration.
Updated documentation to explain the new setup and provide usage instructions.

How was this change tested?

Verified locally by running:

make lint test  # Run Jaeger lint and test checks
npm run lint && npm run test  # Run Jaeger UI checks

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

yurishkuro · 2025-03-18T21:04:40Z

cmd/config-query.yml

@@ -0,0 +1,52 @@
+service:


we already have that cmd/jaeger/config-query.yaml

Thanks for pointing that out! I noticed the existing cmd/jaeger/config-query.yaml. Would you like me to remove the new file, update it if needed, or leave it as is? Let me know how you'd like to proceed!

Don't introduce changes that are not necessary

…g#6683) - Import the nop receiver and exporter - Create a sample query service configuration - Extend E2E tests to validate the new configuration - Update documentation to explain the setup - Provide an example configuration for jaeger-query v2 Signed-off-by: sAchin-680 <[email protected]>

…ng#6863) ## Which problem is this PR solving? - Towards jaegertracing#4739 - This was the only dependency on cmd/agent from other packages. Once the next release of OTEL Contrib lands we can remove cmd/agent. ## Description of the changes - Copy the interface into internal/sampling/http/handler.go ## How was this change tested? - CI Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: sAchin-680 <[email protected]>

…ertracing#6870) This PR contains the following updates: | Package | Update | Change | |---|---|---| | prom/prometheus | digest | `6927e09` -> `502ad90` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/jaegertracing/jaeger).  --------- Signed-off-by: Mend Renovate <[email protected]> Signed-off-by: Yuri Shkuro <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: sAchin-680 <[email protected]>

…reusable for v2 APIs (jaegertracing#6845) ## Which problem is this PR solving? Fixes a part of: jaegertracing#6458 ## Description of the changes - Refactoring of `FindTraces` and `GetTrace` to complete refactoring for ES Span Reader ## 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: sAchin-680 <[email protected]>

Signed-off-by: sAchin-680 <[email protected]>

…ng#6871) This PR contains the following updates: | Package | Update | Change | |---|---|---| | prom/prometheus | patch | `v3.2.0` -> `v3.2.1` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/jaegertracing/jaeger).  Signed-off-by: Mend Renovate <[email protected]> Signed-off-by: sAchin-680 <[email protected]>

## Which problem is this PR solving? - Part of jaegertracing#4739 ## Description of the changes - Remove all remaining agent code: `rm -rf cmd/agent` ## How was this change tested? - CI Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: sAchin-680 <[email protected]>

) ## Which problem is this PR solving? Fixes a part of: jaegertracing#6458 ## Description of the changes - Removal of pointer signatures from `CoreSpanReader` ## 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: sAchin-680 <[email protected]>

## Which problem is this PR solving? - Follow-up to jaegertracing#6494 ## Description of the changes - Remove model files that only contained aliases to jaeger-idl types - model/*go - proto-gen/api_v2/*go - thrift-gen/** ## How was this change tested? - CI --------- Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: sAchin-680 <[email protected]>

…g#6683) jaegertracing#6873 Signed-off-by: sAchin-680 <[email protected]>

…e-6683

yurishkuro · 2025-03-20T13:24:05Z

cmd/jaeger/internal/components.go

 	"github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter"
 	"github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckv2extension"
 	"github.com/open-telemetry/opentelemetry-collector-contrib/processor/attributesprocessor"
 	"github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor"
 	"github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver"
 	"github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkareceiver"
+	"github.com/open-telemetry/opentelemetry-collector-contrib/receiver/nopreceiver"


we already have these from main repo

yurishkuro · 2025-03-20T13:24:35Z

docs/jaeger-query-v2-setup.md

+## What Has Changed?
+-  Jaeger Query v2 Support: Integrated into the CI/CD pipeline.
+- Updated `ci-crossdock.yml` : Includes a step for running Jaeger Query v2.


what is this referring to? changed since when?

yurishkuro · 2025-03-20T13:25:30Z

docs/jaeger-query-v2-setup.md

@@ -0,0 +1,56 @@
+# Jaeger Query v2 Setup Guide


I don't think this file is necessary. The documentation changes should be made on the docs website.

sAchin-680 requested a review from a team as a code owner March 18, 2025 21:02

sAchin-680 requested a review from mahadzaryab1 March 18, 2025 21:02

dosubot bot added area/otel v2 labels Mar 18, 2025

yurishkuro reviewed Mar 18, 2025

View reviewed changes

sAchin-680 force-pushed the feat/jaeger-query-v2-config-e2e-6683 branch from e388773 to f62e87c Compare March 19, 2025 09:13

sAchin-680 and others added 9 commits March 19, 2025 09:20

fix: format indentation in build-crossdock.sh script

f090441

Signed-off-by: sAchin-680 <[email protected]>

sAchin-680 force-pushed the feat/jaeger-query-v2-config-e2e-6683 branch from f62e87c to c8e6980 Compare March 19, 2025 09:32

feat: add sample config & E2E tests for Jaeger Query v2 (jaegertracin…

df1ec13

…g#6683) jaegertracing#6873 Signed-off-by: sAchin-680 <[email protected]>

sAchin-680 force-pushed the feat/jaeger-query-v2-config-e2e-6683 branch from 749392c to df1ec13 Compare March 20, 2025 13:20

Merge branch 'jaegertracing:main' into feat/jaeger-query-v2-config-e2…

d33abb2

…e-6683

yurishkuro reviewed Mar 20, 2025

View reviewed changes

sAchin-680 closed this Mar 20, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873

feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873

Uh oh!

sAchin-680 commented Mar 18, 2025

Uh oh!

yurishkuro Mar 18, 2025

Uh oh!

sAchin-680 Mar 19, 2025

Uh oh!

yurishkuro Mar 19, 2025

Uh oh!

yurishkuro Mar 20, 2025

Uh oh!

yurishkuro Mar 20, 2025

Uh oh!

yurishkuro Mar 20, 2025

Uh oh!

Uh oh!

feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873

feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873

Uh oh!

Conversation

sAchin-680 commented Mar 18, 2025

Key Changes:

Which problem is this PR solving?

Description of the changes

Changes Introduced

How was this change tested?

Checklist

Uh oh!

yurishkuro Mar 18, 2025

Choose a reason for hiding this comment

Uh oh!

sAchin-680 Mar 19, 2025

Choose a reason for hiding this comment

Uh oh!

yurishkuro Mar 19, 2025

Choose a reason for hiding this comment

Uh oh!

yurishkuro Mar 20, 2025

Choose a reason for hiding this comment

Uh oh!

yurishkuro Mar 20, 2025

Choose a reason for hiding this comment

Uh oh!

yurishkuro Mar 20, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!