anchor.diff:  
   See [Binding User-Provided Service Instances to Applications](user-provided.html#cups-example).
   
  -### <a id='verify'></a>Verifying that Logs are Draining Correctly ###
  +## <a id='verify'></a>Step 4: Verify that Logs are Draining Correctly ##
   
   To verify that logs are draining correctly to a third-party log management service:
   
  
positive.code: 
      <p class="note"><strong>Note</strong>: <%=vars.product_short%> does not support using <code>syslog-tls</code> with self-signed certificates. If you are running your own syslog server and want to use <code>syslog-tls</code>, you must have an SSL certificate signed by a well-known certificate authority.</p>
  
  ### <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 ###
  
  You have two options:
  
  
negative.code: 
  _This page assumes you are using cf CLI v6._
  
  Logs record activity in all instances of your applications and in other components of your Cloud Foundry installation. For example, when a Cloud Foundry Router routes an HTTP request to an app, the Router records that event in the application log stream.
  
  The Cloud Foundry [Loggregator](../deploy-apps/streaming-logs.html) component consolidates log information from across your Cloud Foundry installation. Loggregator keeps only a limited quantity of this information, and this information is lost any time the Loggregator is restarted. To keep more log information than what Loggregator stores, you can use a Cloud Foundry compatible third-party log management service, such as Logentries, Logstash, Papertrail, or Splunk. Third-party service also offer tools to analyze the logs. For example, you could produce metrics for application response times or error rates.
  
  Think of the relationship between Cloud Foundry and the third-party logging service in terms of source, sink, and drain:
  
  * Your applications and the Cloud Foundry components that interact with them make up your information **source**.
  * The third-party log management service is an information **sink**.
  * A **drain** configured on the application helps the source communicate with the sink.
  
  ## <a id='config'></a>Step 1: Configure the log management service to treat your application as a source of data ##
  
  You must configure a third-party log management service to accept traffic from your Cloud Foundry environment. See [Configuring Selected Third-Party Log Management Services](log-management-thirdparty-svc.html) for instructions.
  
  Depending on the service provider, you may need the following information:
  
  * The <%=vars.external_ips%> <%=vars.admin%> assigns to outbound traffic.
  