-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Enhancement] Hotrod and Monitor Use Docker Compose V2 as Default #6523
base: main
Are you sure you want to change the base?
Conversation
1ad5347
to
e9b8615
Compare
Signed-off-by: zzzk1 <[email protected]>
e9b8615
to
ff0faea
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6523 +/- ##
==========================================
+ Coverage 96.27% 96.29% +0.01%
==========================================
Files 372 372
Lines 21283 21283
==========================================
+ Hits 20491 20494 +3
+ Misses 605 603 -2
+ Partials 187 186 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Thanks, good start.
@@ -20,7 +20,7 @@ build: clean-jaeger | |||
.PHONY: dev | |||
dev: export JAEGER_IMAGE_TAG = dev | |||
dev: | |||
docker compose -f docker-compose.yml up $(DOCKER_COMPOSE_ARGS) | |||
docker compose -f docker-compose-v1.yml up $(DOCKER_COMPOSE_ARGS) | |||
|
|||
.PHONY: dev-v2 |
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.
Can we change the target names accordingly? And the readme.
@@ -69,7 +69,7 @@ This brings up the system necessary to use the SPM feature locally. | |||
It uses the latest image tags from both Jaeger and OpenTelemetry. | |||
|
|||
```shell | |||
docker compose up | |||
docker compose -f docker-compose-v1.yml up |
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.
Let's turn this around and emphasize v2 first, with a note for v1
@@ -83,7 +83,7 @@ docker compose -f docker-compose-v2.yml up | |||
- Navigate to Jaeger UI at http://localhost:16686/ and inspect the Monitor tab. Select `redis` service from the dropdown to see more than one endpoint. | |||
- To visualize the raw metrics stored on the Prometheus server (for debugging and local development use cases), use the built-in Prometheus UI at http://localhost:9090/query. For example, http://localhost:9090/query?g0.expr=traces_span_metrics_calls_total&g0.tab=0&g0.range_input=5m | |||
|
|||
**Warning:** The included [docker-compose.yml](./docker-compose.yml) file uses the `latest` version of Jaeger and other components. If your local Docker registry already contains older versions, which may still be tagged as `latest`, you may want to delete those images before running the full set, to ensure consistent behavior: | |||
**Warning:** The included [docker-compose-v1.yml](./docker-compose-v1.yml) file uses the `latest` version of Jaeger and other components. If your local Docker registry already contains older versions, which may still be tagged as `latest`, you may want to delete those images before running the full set, to ensure consistent behavior: |
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.
**Warning:** The included [docker-compose-v1.yml](./docker-compose-v1.yml) file uses the `latest` version of Jaeger and other components. If your local Docker registry already contains older versions, which may still be tagged as `latest`, you may want to delete those images before running the full set, to ensure consistent behavior: | |
**Warning:** The included ` docker compose` files use the `latest` version of Jaeger and other components. If your local Docker registry already contains older versions, which may still be tagged as `latest`, you may want to delete those images before running the full set, to ensure consistent behavior: |
@@ -126,7 +126,7 @@ to emit traces to the OpenTelemetry Collector which, in turn, will aggregate the | |||
|
|||
Start the local stack needed for SPM, if not already done: | |||
```shell | |||
docker compose up | |||
docker compose -f docker-compose-v2.yml up |
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.
The v2 files need to be renamed just docker-compose, so that the user is not required to specify them on the command line.
@@ -23,7 +23,7 @@ As of Jaeger v1.42.0 this application was upgraded to use the OpenTelemetry SDK | |||
|
|||
### Run everything via `docker compose` | |||
|
|||
* Download `docker-compose.yml` from https://github.com/jaegertracing/jaeger/blob/main/examples/hotrod/docker-compose.yml | |||
* Download `docker-compose-v1.yml` from https://github.com/jaegertracing/jaeger/blob/main/examples/hotrod/docker-compose-v1.yml |
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.
Emphasize v2 versions in the docs, not v1
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