Enabling Zipkin Tracing

Page last updated:

Warning: Pivotal Cloud Foundry (PCF) v2.3 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

Zipkin is a tracing system that enables app developers to troubleshoot failures or latency issues. Zipkin provides the ability to trace requests and responses across distributed systems. See Zipkin.io for more information.

Zipkin tracing is enabled by default in PCF.

To disable this feature, select the PAS Tile in Ops Manager, and click on Networking deselect the Enable Zipkin tracing headers on the router. For example, see Deploying PAS on GCP for instructions on how to modify this setting on GCP.

For more information about how the Gorouter works with HTTP headers and Zipkin tracing, see the HTTP Headers section of the HTTP Routing topic.

To trace app requests and responses in Cloud Foundry, 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 applications.