Skip to content

Commit dae5e30

Browse files
Updated the docs
1 parent 79d7cec commit dae5e30

File tree

3 files changed

+17
-24
lines changed

3 files changed

+17
-24
lines changed

spring-cloud-sleuth-samples/README.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,10 @@ image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master
3535

3636
Instead of POSTing trace data directly to a Zipkin server, you can export them over https://raw.githubusercontent.com/spring-cloud/spring-cloud-stream[Spring Cloud Stream].
3737

38-
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).
38+
1. Run the RabbitMQ middleware for Zipkin (you can use `docker-compose.yml`).
39+
2. Build the Zipkin Stream sample with Maven and run it.
3940
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`.
40-
9. Go to `http://localhost:9411` for Zipkin's UI (if you are using boot2docker the host will be different)
41+
9. Go to `http://localhost:9411` for Zipkin's UI
4142

4243
The UI should look more or less like this:
4344

Lines changed: 7 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,15 @@
11
# Running a Zipkin Server
22

3-
There are 3 parts to Zipkin: the instrumented client apps, the backend database and the Zipkin server. The database for this implementation is MySQL.
4-
5-
## Zipkin Services
6-
7-
Run this app using the docker-compose provided.
8-
9-
```
10-
$ docker-compose build zipkin
11-
$ docker-compose up
12-
...
13-
```
14-
15-
and test it
16-
17-
```
18-
$ curl localhost:9411/api/v1/services
19-
["zipkin-query"]
20-
```
21-
22-
The app might fail to start if mysql is not available when it needs it. If that happens you can just start it separately: just keep running `docker-compose up` until it works.
3+
There are 3 parts to Zipkin:
234

5+
- the instrumented client apps
6+
- the backend database
7+
- the Zipkin server
248

259
## Instrumenting Apps
2610

27-
Depend on [Spring Cloud Sleuth Stream](https://github.com/spring-cloud-spring-cloud-sleuth) and the rabbit binder (`spring-cloud-starter-stream-rabbit`).
11+
Depend on [Spring Cloud Sleuth Stream](https://github.com/spring-cloud-spring-cloud-sleuth) and the
12+
rabbit binder (`spring-cloud-starter-stream-rabbit`).
2813

2914
Once the apps start publishing spans they will appear in the span store as well.
3015

@@ -33,5 +18,5 @@ Once the apps start publishing spans they will appear in the span store as well.
3318
You can run this app in an IDE and still use docker-compose to create the middleware:
3419

3520
```
36-
$ docker-compose up rabbitmq mysql
21+
$ docker-compose up rabbitmq
3722
```
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
rabbitmq:
2+
image: rabbitmq:management
3+
expose:
4+
- 5672
5+
ports:
6+
- 5672:5672
7+
- 15672:15672

0 commit comments

Comments
 (0)