anchor.diff:  
   ## <a id='use'></a>Using a Third-Party Log Management Service ##
   
  -To drain logs to a third-party log management service from an application and the relevant Cloud Foundry components, you complete three steps.
  -In general terms, the process looks like this:
  +The overall process of enabling your application and the relevant Cloud Foundry components to drain logs to a third-party log management service looks like this:
   
   1. Configure the log management solution to treat your application as a source of data.
   
  
positive.code: 
  1. `cf logs <app_name> --recent` Displays all the logging information that Loggregator possesses at that moment.
  
  	`cf logs <app_name> --recent`  TBD
  
  1. Filter log messages by log type. The possibilities are described in Types of Logs below. Our example filters for the second instance of an app (APP/1).
  
  1. Filter log messages by channel. The two possibilities are standard out (`STD`)  and standard error (`ERR`). Our example filters for ERR messages only.
  
  
negative.code: 	</tbody>
  </table>
  
  ## <a id='format'></a> The Syslog Protocol and How Syslog Messages are Transmitted  ##
  
  Loggregator formats logging data that it sends to third-party services according to [RFC 5424](http://tools.ietf.org/html/rfc5424), titled *The Syslog Protocol*.
  Logs viewed in the CLI are not in syslog format.
  