forked from cloudfoundry/docs-cf-admin
-
Notifications
You must be signed in to change notification settings - Fork 0
/
zipkin_tracing.html.md.erb
31 lines (18 loc) · 1.2 KB
/
zipkin_tracing.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
---
title: Enabling Zipkin tracing in Cloud Foundry
owner: CF for VMs Networking
---
<%# Reset page title based on platform type %>
<% if vars.platform_code != 'CF' %>
<% set_title("Enabling Zipkin tracing in", vars.app_runtime_abbr) %>
<% end %>
You can use Zipkin tracing to troubleshoot failures or latency issues in your apps. You can trace requests and responses
across distributed systems. For more information, see [Zipkin.io](http://zipkin.io/).
<% if vars.platform_code != "CF" %>
<%= partial "/pcf/core/zipkin-pcf-config" %>
<% else %>
<%= partial "zipkin_oss_config" %>
<% end %>
For more information about how the Gorouter works with HTTP headers and Zipkin tracing, see the [HTTP Headers](../concepts/http-routing.html#http-headers) section of the _HTTP Routing_ topic.
To trace app requests and responses in <%= vars.app_runtime_first %>, apps must also log Zipkin headers.
After adding Zipkin HTTP headers to app logs, developers can use `cf logs myapp` to correlate the trace and span IDs logged by the Gorouter with the trace IDs logged by their app. To correlate trace IDs for a request through multiple apps, each app must forward appropriate values for the headers with requests to other apps.