-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat: add sample config & E2E tests for jaeger-query v2 (#6683) #6873
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
Closed
sAchin-680
wants to merge
11
commits into
jaegertracing:main
from
sAchin-680:feat/jaeger-query-v2-config-e2e-6683
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
86b107f
feat: add sample config & E2E tests for jaeger-query v2 (#6683)
sAchin-680 5c62cef
[refactor] Move interface to remove cmd/agent dependency (#6863)
yurishkuro dca60d4
chore(deps): pin prom/prometheus:latest docker to v3.2.0 + hash (#6870)
renovate-bot 9211aff
[ES] Refactor `FindTraces` and `GetTrace` of SpanReader to make them …
Manik2708 f090441
fix: format indentation in build-crossdock.sh script
sAchin-680 72cbb05
chore(deps): update prom/prometheus docker tag to v3.2.1 (#6871)
renovate-bot 08d7463
🪦 Remove Agent code (#6868)
yurishkuro f00df84
[ES] Remove pointer signatures from `CoreSpanReader` (#6874)
Manik2708 c8e6980
Cleanup legacy models (#6875)
yurishkuro df1ec13
feat: add sample config & E2E tests for Jaeger Query v2 (#6683) #6873
sAchin-680 d33abb2
Merge branch 'jaegertracing:main' into feat/jaeger-query-v2-config-e2…
sAchin-680 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
# Jaeger Query v2 Setup Guide | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this file is necessary. The documentation changes should be made on the docs website. |
||
|
||
## Overview | ||
This guide explains the integration of Jaeger Query v2 into the Jaeger project. It includes details on the updated configuration, CI workflow, and how to use the new setup effectively. | ||
|
||
## 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. | ||
Comment on lines
+6
to
+8
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what is this referring to? changed since when? |
||
|
||
## How to Use the New Configuration | ||
### 1. Configuration File | ||
- The configuration file is located at `cmd/config-query.yml`. | ||
- Key changes include: | ||
- Support for in-memory storage. | ||
- Prometheus metrics configuration. | ||
- UI static files and index file setup. | ||
|
||
### 2. Running Jaeger Query v2 | ||
- Use the following command to run Jaeger Query v2: | ||
```bash | ||
docker run -d \ | ||
--name jaeger-query-v2 \ | ||
--rm \ | ||
-p 16686:16686 \ # UI port | ||
-p 16685:16685 \ # Query service port | ||
-v ./cmd/jaeger/config.yaml:/etc/jaeger/config.yaml \ | ||
jaegertracing/all-in-one:latest \ | ||
--query.base-path=/jaeger | ||
``` | ||
|
||
### 3. CI Workflow Integration | ||
The CI workflow (`ci-crossdock.yml`) has been updated to: | ||
- Include a step for running Jaeger Query v2 during testing. | ||
- Ensure tests run against the new configuration. | ||
|
||
## Additional Notes | ||
- For more details, refer to the [`README.md`](/docs/jaeger-query-v2-setup.md) and [`CONTRIBUTING.md`](CONTRIBUTING.md) files as per the Jaeger documentation. | ||
|
||
<!-- ## Troubleshooting | ||
- If you encounter issues with the configuration, verify that the `config-query.yml` file is correctly mounted in the container. | ||
- Ensure that the required ports (`16686` and `16685`) are not in use by other services. --> | ||
|
||
# Troubleshooting Jaeger Query v2 | ||
|
||
Jaeger Query v2 is not starting? | ||
- Check that `config-query.yml` is correctly mounted in the container. | ||
- Ensure required ports (`16686`, `16685`) are available. | ||
|
||
No traces appearing in the UI? | ||
- Verify the **storage backend configuration** in `config-query.yml`. | ||
- Confirm that your application is sending traces to Jaeger. | ||
|
||
CI/CD workflow failing? | ||
- Run the following command to inspect logs for errors: | ||
```bash | ||
docker logs jaeger-query-v2 |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
we already have these from main repo