anchor.diff:  
   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.
  +For example, when a Cloud Foundry Router routes an HTTP request to an app, the Router records that event in the application log stream.
   
  -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.
  +Cloud Foundry keeps a limited amount of logging information in memory.
  +When you want to persist more log information than this, you must 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.
  +Providers whose log management products or services have been verified to work with syslog output include [Logentries](https://logentries.com/), [logstash](http://logstash.net/), [Papertrail](https://papertrailapp.com/), and [Splunk](http://www.splunk.com/).
   
   You can think of the relationship between Cloud Foundry and the third-party logging service in terms of source, sink, and drain:
   
  
positive.code: 
  Details about each of these steps follow.
  
  ### <a id='cli'></a>Observing the logs for your application ###
  
  It's a good idea to become familiar with the log messages your application and relevant system components generate.
  [Use the CLI](../deploy-apps/streaming-logs.html#view) to explore what kinds of messages are generated by various application behaviors.
  Then you are better prepared to understand what you see in a third-party log management service.
  See [Viewing Logs in the Command Line Interface](../deploy-apps/streaming-logs.html#view).
  
  ### <a id='config'></a>Configuring the log management service to treat your application as a source of data ###
  
  Typically, you must configure a third-party log management service to accept traffic from your Cloud Foundry.
  Depending on the service provider, you may need the following information:
  
  * The external IP addresses <%=vars.admin%> assigns to outbound traffic<%=vars.log_drain%>
  
  * The syslog URL, a special URL that the service typically makes available as an endpoint for incoming log data.
  Cloud Foundry uses the syslog URL to route messages to the service.
  
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 ###
  
  