anchor.diff:  
   ## <a id='container-metrics'></a> Including Container Metrics in Syslog Drains
   
  -By default, app logs are included in syslog drains. Syslog Agents forward logs to configured syslog drains and Loggregator. For more information about Syslog Agents, see the [Loggregator Components](https://docs.cloudfoundry.org/loggregator/architecture.html#loggregator-components) section of the _Loggregator Architecture_ topic.
  +By default, app logs are included in syslog drains. Syslog Agents forward logs to configured syslog drains and Loggregator. For more information about Syslog Agents, see [Loggregator Components](https://docs.cloudfoundry.org/loggregator/architecture.html#loggregator-components) in _Loggregator Architecture_.
   
   
   ## <a id='view'></a> Viewing Logs in the Command Line Interface
  
positive.code: 
  ### <a id="filter"></a> Filtering Logs
  
  To view some subset of log output, run `cf logs APP-NAME` in conjunction with filtering commands of your choice. Replace `APP-NAME` with the name of your app. In the example below, `grep -v RTR` excludes all Router logs:
  
  <pre class="terminal">
  $ cf logs spring-music --recent | grep -v RTR
  
negative.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 [Zipkin Tracking in HTTP Headers](../../concepts/http-routing.html#zipkin-headers) in _HTTP Routing_.
  
  ### <a id='lgr'></a> LGR
  
  