Scrubs docs about zipkin-web as it is now embedded
This commit is contained in:
@@ -10,7 +10,7 @@ There are a few samples with slightly different features. You can run all of the
|
||||
|
||||
* `spring-cloud-sleuth-sample-stream`: same as vanilla sample, but exports span data to RabbitMQ using Spring Cloud Stream
|
||||
|
||||
* `spring-cloud-sleuth-sample-stream-zipkin`: a consumer for the span data on RabbitMQ that pushes it into a Zipkin span store, so it can be queried and visualized using the standard Zipkin UI.
|
||||
* `spring-cloud-sleuth-sample-stream-zipkin`: a consumer for the span data on RabbitMQ that pushes it into a Zipkin span store, so it can be queried and visualized using the embedded Zipkin UI.
|
||||
|
||||
* `spring-cloud-sleuth-sample-messaging`: a Spring Integration application with two HTTP endpoints ("/" and "/xform")
|
||||
|
||||
@@ -20,10 +20,10 @@ The Ribbon sample makes an interesting demo or playground for learning about zip
|
||||
|
||||
=== Running samples with Zipkin
|
||||
|
||||
1. Optionally run the https://github.com/openzipkin/zipkin[Zipkin] UI, e.g. via docker compose (there's a `docker-compose.yml` in https://github.com/spring-cloud/spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin[Spring Cloud Sleuth], or in https://github.com/openzipkin/docker-zipkin[Docker Zipkin]
|
||||
1. Optionally run the https://github.com/openzipkin/zipkin[Zipkin] Server, e.g. via docker compose (there's a `docker-compose.yml` in https://github.com/spring-cloud/spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin[Spring Cloud Sleuth], or in https://github.com/openzipkin/docker-zipkin[Docker Zipkin]
|
||||
7. Run the zipkin sample application (set `sample.zipkin.enabled=false` if you have no Zipkin running). If you are using a VM to run docker you might need to tunnel port 9411 to localhost, or change the `spring.zipkin.baseUrl`.
|
||||
8. Hit `http://localhost:3380`, `http://localhost:3380/call`, `http://localhost:3380/async` for some interesting sample traces (the app callas back to itself).
|
||||
9. Goto `http://localhost:8080` for zipkin web (if you are using boot2docker the host will be different)
|
||||
9. Go to `http://localhost:9411` for Zipkin's UI (if you are using boot2docker the host will be different)
|
||||
|
||||
NOTE: You can see the zipkin spans without the UI (in logs) if you run the sample with `sample.zipkin.enabled=false`.
|
||||
|
||||
@@ -37,8 +37,8 @@ Instead of POSTing trace data directly to a Zipkin server, you can export them o
|
||||
|
||||
1. Build the Zipkin Stream sample with Maven and run it via its `docker-compose.yml` (which also starts the required middleware and the Zipkin UI).
|
||||
7. Run the `spring-cloud-sleuth-sample-stream` app and interact with it in a browser, just like the vanilla sample. If you are using a VM to run docker you might need to tunnel port 5672 to localhost, or change the `spring.rabbbitmq.host`.
|
||||
9. Goto `http://localhost:8080` for zipkin web (if you are using a VM to run docker the host will be different).
|
||||
9. Go to `http://localhost:9411` for Zipkin's UI (if you are using boot2docker the host will be different)
|
||||
|
||||
The UI should look more or less like this:
|
||||
|
||||
image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/docs/src/main/asciidoc/images/zipkin-traces.png[Zipkin Web Screenshot]
|
||||
image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/docs/src/main/asciidoc/images/zipkin-traces.png[Zipkin Web Screenshot]
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Running a Zipkin Query Server
|
||||
# Running a Zipkin Server
|
||||
|
||||
There are 4 parts to Zipkin: the instrumented client apps, the web UI, the backend database and the query server. The database for this implementation is MySQL.
|
||||
There are 3 parts to Zipkin: the instrumented client apps, the backend database and the Zipkin server. The database for this implementation is MySQL.
|
||||
|
||||
## Zipkin Services
|
||||
|
||||
@@ -35,5 +35,3 @@ You can run this app in an IDE and still use docker-compose to create the middle
|
||||
```
|
||||
$ docker-compose up rabbitmq mysql
|
||||
```
|
||||
|
||||
The web UI cannot access the docker host though, so you have to run that separately, or just test against the query server directly on port 9411.
|
||||
|
||||
Reference in New Issue
Block a user