anchor.diff:  2020-01-13T16:12:25.86-0800 [APP/PROC/WEB/0] OUT app instance exceeded log rate limit (100 log-lines/sec) set by platform operator
   </pre>
   
  -This message only appears if the limit has been set by a platform operator.
  -<%= vars.app_log_limit_config %>
  +This message only appears if the limit has been set by a platform operator. <%= vars.app_log_limit_config %>
   
   ## <a id='writing'></a> Writing to the Log from Your App
   
  
positive.code: 2016-11-23T16:04:01.49-0800 [RTR/0]      OUT www.example.com - [24/11/2016:00:04:01.227 +0000] "GET / HTTP/1.1" 200 0 109 "-" "curl/7.43.0" 10.0.2.150:4070 10.0.48.66:60815 x_forwarded_for:"198.51.100.120" x_forwarded_proto:"http" vcap_request_id:87f9d899-c7a4-46cd-7b76-4ec35ce9921b response_time:0.263000966 app_id:8e5d6451-b369-4423-bce8-3a7a9e479dbb app_index:0 x_b3_traceid:"2d5610bf5e0f7241" x_b3_spanid:"2d5610bf5e0f7241" x_b3_parentspanid:"-"
  </pre>
  
  For more information about Zipkin tracing, see the [Zipkin Tracking in HTTP Headers](../../concepts/http-routing.html#zipkin-headers) section of the _HTTP Routing_ topic.
  
  ### <a id='lgr'></a> LGR
  
  
negative.code: 
  ### <a id='rtr'></a> RTR
  
  The Gorouter emits RTR logs when it routes HTTP requests to the app. Gorouter messages include the app name followed by a Gorouter timestamp and selections from the HTTP request.
  
  For example:
  
  