@@ -687,9 +687,9 @@ In that case, you might want to have your Hystrix commands push metrics to Turbi
To do so on the client, add a dependency to `spring-cloud-netflix-hystrix-stream` and the `spring-cloud-starter-stream-*` of your choice.
See the https://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/[Spring Cloud Stream documentation] for details on the brokers and how to configure the client credentials. It should work out of the box for a local broker.
On the server side, create a Spring Boot application and annotate it with `@EnableTurbineStream`. By default, it starts on port 8989 (point your Hystrix dashboard to that port on any path).
You can customize the port by setting `server.port`.
The Turbine Stream server requires the use of Spring Webflux, therefor `spring-boot-starter-webflux` needs to be included in your project.
On the server side, create a Spring Boot application and annotate it with `@EnableTurbineStream`.
The Turbine Stream server requires the use of Spring Webflux, therefore `spring-boot-starter-webflux` needs to be included in your project.
By default `spring-boot-starter-webflux` is included when adding `spring-cloud-starter-netflix-turbine-stream` to your application.
You can then point the Hystrix Dashboard to the Turbine Stream Server instead of individual Hystrix streams.
If Turbine Stream is running on port 8989 on myhost, then put `http://myhost:8989` in the stream input field in the Hystrix Dashboard.
