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.

Sign up for GitHub

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

Jump to bottom

Create example configuration for jaeger-query v2 #6683

Open
4 tasks
yurishkuro opened this issue Feb 6, 2025 · 1 comment
Open
4 tasks

Create example configuration for jaeger-query v2 #6683

yurishkuro opened this issue Feb 6, 2025 · 1 comment
Labels
documentation good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2

Comments

@yurishkuro
Copy link
Member

Per https://github.com/orgs/jaegertracing/discussions/6682

Jaeger query as a role does not require the ingestion pipeline, only the query service, but the OTEL Collector architecture does not support that, it requires a minimum pipeline. OTEL Collector does provide nop receiver and exporter that can be used to define a dummy pipeline, but we did not import them in our components.go

  • import nop receiver and exporter
  • create a sample query service configuration
  • extend our e2e integration tests to exercise this new configuration (the ci-crossdock.yml already does it but with v1 components, we can extend it to do v2)
  • update documentation website to explain the configuration
@yurishkuro yurishkuro added good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement labels Feb 6, 2025
@danish9039
Copy link
Contributor

working on it

@danish9039 danish9039 mentioned this issue Feb 6, 2025
Merged
4 tasks
yurishkuro added a commit that referenced this issue Feb 8, 2025
@danish9039 @yurishkuro
Import nop receiver/exporter and add a sample query service config (#…
8def385 
…6687)

## Which problem is this PR solving?
- part of #6683

## Description of the changes
- import `nop `receiver ,exporter and create a sample query service
configuration named `config-query.yaml`


## How was this change tested?
- 

## 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: danish9039 <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yurishkuro @danish9039