anchor.diff:  ---
  -title: Using Third-Party Log Management Services
  +title: Third-Party Log Management Services
   ---
   
   _This page assumes that you are using cf v6._
   
   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 the application log stream.
  +For example, when a Cloud Foundry Router routes an HTTP request to an app, the Router records that event in a log.
   
  -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.
  +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.
   
  -<<<<<<< HEAD
  -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/).
  -=======
   Providers whose log management products or services work with Cloud Foundry include Logentries, logstash, Papertrail, and Splunk. You will need to [setup an appropriate connection with these services for use with Cloud Foundry](log-management-thirdparty-svc.html).
  ->>>>>>> b3a428f336abf647c435bdac8fb883aac4b4846e
   
   You can think of the relationship between Cloud Foundry and the third-party logging service in terms of source, sink, and drain:
   
  
positive.code: 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.
  
negative.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 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.
  
  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.
  
  ## <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.
  
  