anchor.diff:  
   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.
  +Typically, you must configure a third-party log management service to accept traffic from your Cloud Foundry environment.
   Depending on the service provider, you may need the following information:
   
   * The external IP addresses <%=vars.admin%> assigns to outbound traffic<%=vars.log_drain%>
  +
  +    **Note**: You must whitelist all of these IP addresses. Allowing traffic from a subset of the external IP addresses assigned to outbound traffic restricts the logs that are available to third party services.
   
   * 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.
  
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: 
  To verify that logs are draining correctly to a third-party log management service:
  
  1. Take actions that you believe should produce log messages, such as making requests of your app.
  
  1. Compare the logs you see in the CLI against those that the service shows you.
  
  