anchor.diff:  
   ### <a id='zipkin_trace'></a> Analyze Zipkin Trace IDs
   
  -When the Zipkin feature is enabled in Cloud Foundry, the Gorouter adds or forwards Zipkin trace IDs and span IDs to HTTP headers. For more information about what the Gorouter provides in the HTTP header, see the [HTTP Headers](../../concepts/http-routing.html#http-headers) section of the _HTTP Routing_ topic.
  +When the Zipkin feature is enabled in <%= vars.platform_name %>, the Gorouter adds or forwards Zipkin trace IDs and span IDs to HTTP headers. For more information about what the Gorouter provides in the HTTP header, see the [HTTP Headers](../../concepts/http-routing.html#http-headers) section of the _HTTP Routing_ topic.
   
   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.
   
  
positive.code: 
  Even when the deploy fails, the app might exist on <%=vars.product_short%>. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
  
  If you push multiple apps using a manifest and one fails to deploy, CF does not attempt to push apps specified after the app that failed. 
  
  Common reasons deploying an app fails include:
  
  
negative.code: 
  <% $this_topic = 'troubleshoot-app-health' %>
  
  See this topic for help diagnosing and resolving common issues when you deploy and run apps on <%= vars.platform_name %>.
  
  
  ## <a id='scenarios'></a> Common Issues
  