anchor.diff:  In Cloud Foundry, these generate Router log messages, which you can view in the CLI.
   The third-party logging service should show you corresponding messages, although probably in a different format.
   
  -**Note**: For security reasons, Cloud Foundry applications do not respond to ping, so you cannot use ping to generate log entries.
  +**Note**: For security reasons, Cloud Foundry applications do not respond to ping, so you cannot use ping to generate log entries.
positive.code: ## <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 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 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. Configure the log management service to treat your application as a source of data.
  
  
negative.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 of the two NAT boxes from which Cloud Foundry will send log traffic to the service.
  Ask your Cloud Foundry administrator for these IP addresses.
  (NAT boxes are systems responsible for Network Address Translation, not to be confused with the NATS messaging protocol.)
  
  * 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.
  The syslog URL has a scheme of `syslog` or `syslog-tls` and includes a port number.
  For example:
  
   `syslog://logs.example.com:1234`
  
  TLS support is described in [RFC 5425](http://tools.ietf.org/html/rfc5425).
  
  ### <a id='create'></a>Creating a user-provided service instance with a syslog drain ###
  
  Create a user-provided service instance using the `cups` command with the `-l` option and the syslog URL you obtained earlier.
  The `-l` option configures the syslog drain.
  See [User-Provided Services] (./user-provided.html#user-cups).
  
  ### <a id='bind'></a>Binding the service instance to the application ###
  
  