anchor.diff:  ## <a id='loggregator'></a>Loggregator ##
   
   The Loggregator component of Cloud Foundry consolidates the logs of all actions that directly affect the app.
  -Loggregator keeps a limited amount of logging information in memory.
  -Eventually the newest logging information replaces the oldest.
  -If forced to restart, Loggregator retains no logging information from before the restart.
  +Loggregator keeps a limited amount of app log data in memory.
  +Eventually the newest log lines replace the oldest.
  +Since all log data is stored transiently in memory, restarting the loggregator service loses any log data that you have not exported.
   
   When sending logs to third-party services, Loggregator formats the data according to the *Syslog Protocol* defined in [RFC 5424](http://tools.ietf.org/html/rfc5424).
   Third-Party Log Management Software is defined in [RFC 6587](http://tools.ietf.org/html/rfc6587).
   
  -In the Command Line Interface (CLI), you can view the entire Loggregator output or filter it to select a subset of logging information.
  -Logs viewed in the CLI are not in syslog format.
  +In the Command Line Interface (CLI), you can stream an app log or view the most recent log data in memory.
  +Logs viewed in the CLI are not in syslog format, and do not exactly match the output to third party services.
   
   ## <a id='use'></a>Draining Logs to a Third-Party Log Management Service ##
   
   To drain logs from your application and relevant Cloud Foundry components to a third-party log management service, complete this procedure:
  -
  -1. Observe the logs for your application.
   
   1. Configure the log management service to treat your application as a source of data.
   
  
positive.code: 
  Logs tell you both what your app does and what the system does with your app.
  For any one application, logs come from each instance of the app and also from Cloud Foundry system components.
  For example, when a Cloud Foundry Router routes an HTTP request to an app, the Router records that event in a log.
  
  Cloud Foundry is configured to keep a limited amount of logging information in memory.
  When you want to persist more log information than this, you can drain logs to a third-party log management service.
  You can then use the third-party service to analyze the logs.
  For example, you could produce metrics for application response times or error rates.
  
  Providers whose log management products or services work with Cloud Foundry include Logentries, logstash, Papertrail, and Splunk.
  
  You can think of the relationship between Cloud Foundry and the third-party logging service in terms of source, sink, and drain:
  
  
negative.code: 
  ### <a id='create'></a>Creating a user-provided service instance with a syslog drain ###
  
  Create a user-provided service instance using the `create-user-provided-service` command with the `-l` option and the syslog URL you obtained earlier.
  The `-l` option configures the syslog drain.
  Refer to the [User-Provided Services](./user-provided.html#user-cups) topic for more information.
  
  ### <a id='bind'></a>Binding the service instance to the application ###
  
  