spring/spring-cloud-netflix
1
0
Fork 0
mirror of https://github.com/spring-cloud/spring-cloud-netflix.git synced 2026-10-10 06:29:00 +00:00
Code Issues Projects Releases Wiki Activity

Sync docs from master to gh-pages

Browse Source
This commit is contained in:
buildmaster
2016-09-16 19:18:11 +00:00
parent 542e092850
commit 16bdddb025
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spring-cloud-netflix.html
+21
View File
@@ -1163,6 +1163,27 @@ for details on setting up your build system with the current Spring Cloud Releas
<div class="paragraph">
<p>Looking at an individual instances Hystrix data is not very useful in terms of the overall health of the system. <a href="https://github.com/Netflix/Turbine">Turbine</a> is an application that aggregates all of the relevant <code>/hystrix.stream</code> endpoints into a combined <code>/turbine.stream</code> for use in the Hystrix Dashboard. Individual instances are located via Eureka. Running Turbine is as simple as annotating your main class with the <code>@EnableTurbine</code> annotation (e.g. using spring-cloud-starter-turbine to set up the classpath). All of the documented configuration properties from <a href="https://github.com/Netflix/Turbine/wiki/Configuration-(1.x)">the Turbine 1 wiki</a> apply. The only difference is that the <code>turbine.instanceUrlSuffix</code> does not need the port prepended as this is handled automatically unless <code>turbine.instanceInsertPort=false</code>.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
By default, Turbine looks for the <code>/hystrix.stream</code> endpoint on a registered instance by looking up its <code>homePageUrl</code> entry in Eureka, then appending <code>/hystrix.stream</code> to it. This means that if <code>spring-boot-actuator</code> is running on its own port (which is the default), the call to <code>/hystrix.stream</code> will fail.
To make turbine find the Hystrix stream at the correct port, you need to add <code>management.port</code> to the instances' metadata:
</td>
</tr>
</table>
</div>
<div class="listingblock">
<div class="content">
<pre>eureka:
instance:
metadata-map:
management.port: ${management.port:8081}</pre>
</div>
</div>
<div class="paragraph">
<p>The configuration key <code>turbine.appConfig</code> is a list of eureka serviceIds that turbine will use to lookup instances. The turbine stream is then used in the Hystrix dashboard using a url that looks like: <code><a href="http://my.turbine.sever:8080/turbine.stream?cluster=&lt;CLUSTERNAME&gt" class="bare">http://my.turbine.sever:8080/turbine.stream?cluster=&lt;CLUSTERNAME&gt</a>;</code> (the cluster parameter can be omitted if the name is "default"). The <code>cluster</code> parameter must match an entry in <code>turbine.aggregator.clusterConfig</code>. Values returned from eureka are uppercase, thus we expect this example to work if there is an app registered with Eureka called "customers":</p>
</div>