anchor.diff:  
   ## <a id='user-provided'></a>Using Services Not Available in Your Marketplace
   
  -If a compatible log management service is not available in your Cloud Foundry marketplace, you can use [User-provided Service Instances](./user-provided.html#syslog) to stream application logs to a service of your choice.
  +If a compatible log management service is not available in your Cloud Foundry marketplace, you can use [user-provided service instances](./user-provided.html#syslog) to stream application logs to a service of your choice.
   
  -Your service may require some preparation before application logs can be streamed to it from Cloud Foundry. For specific instructions for several popular services, see [Service-Specific Instructions for Streaming Application Logs](./log-management-thirdparty-svc.html). If you cannot find instructions for your service, follow the generic instructions below.
  +You can install and use the [CF Drain CLI Plugin](#drain-plugin) to create and manage user-provided syslog drains from the CF command-line interface (cf CLI).
   
  -### Step 1: Configure the Log Management Service
  +You may need to prepare your log management service to receive app logs from Cloud Foundry. For specific instructions for several popular services, see [Service-Specific Instructions for Streaming Application Logs](./log-management-thirdparty-svc.html). If you cannot find instructions for your service, follow the generic instructions below.
  +
  +### <a id='step1'></a>Step 1: Configure the Log Management Service
   
   Complete the following steps to set up a communication channel between the log management service and your Cloud Foundry deployment:
   
  
positive.code: Your third-party log management service should display corresponding messages.
  
  <p class="note"><strong>Note</strong>: For security reasons, Cloud Foundry applications do not respond to <code>ping</code>. You cannot use <code>ping</code> to generate log entries.</p>
  
negative.code: 
  <%=vars.pas_ssl_note%>
  
  ### <a id='step2'></a>Step 2: Create and Bind a User-Provided Service Instance
  
  You can create a syslog drain service and bind apps to it using either generic Cloud Foundry Command Line Interface (cf CLI) commands, or drain-specific commands enabled by the CF Drain plugin for the cf CLI.
  
  Each option is described below.
  
  #### <a id='drain-plugin'></a>With the CF Drain CLI Plugin
  
  1. If the CF Drain CLI Plugin is not installed on your local workstation, follow the [Installing Plugin](https://github.com/cloudfoundry/cf-drain-cli#installing-plugin) instructions in the plugin source repo.
  
  2. Run `cf create-drain APP-NAME DRAIN-NAME SYSLOG-DRAIN-URL`, filling in values as follows:
    - APP-NAME: The name of the app to stream logs from
    - DRAIN-NAME: A name to use for your syslog drain service instance
    - SYSLOG-DRAIN-URL: The syslog URL from [Step 1: Configure the Log Management Service](#step1).
  
  After a short delay, logs begin to flow automatically.
  
  Refer to the [Usage](https://github.com/cloudfoundry/cf-drain-cli#installing-plugin) section of the CF Drain plugin source repo for CF Drain commands, and [Managing Service Instances with the CLI](./managing-services.html) for general CF service commands.
  
  #### <a id='no-plugin'></a>With General cf CLI Service Commands
  
  1. To create the service instance, run `cf create-user-provided-service` (or `cf cups`) with the `-l` flag, filling in values as follows:
    - DRAIN-NAME: A name to use for your syslog drain service instance
    - SYSLOG-DRAIN-URL: The syslog URL from [Step 1: Configure the Log Management Service](#step1).
  <pre class="terminal">
  $ cf create-user-provided-service DRAIN-NAME -l SYSLOG-URL
  </pre>
  See [User-Provided Service Instances](./user-provided.html) for more information.
  
  1. To bind an app to the service instance, do one of the following:
    * Run `cf push` with a manifest. The services block in the manifest must specify the service instance that you want to bind.
    * Run `cf bind-service`
  <pre class="terminal">
  $ cf bind-service YOUR-APP-NAME DRAIN-NAME
  </pre>
  
  After a short delay, logs begin to flow automatically.
  
  Refer to [Managing Service Instances with the CLI](./managing-services.html) for more information.
  
  ### <a id='cups-step3'></a>Step 3: Verify Logs Are Draining
  
  To verify that logs are draining correctly to a third-party log management service:
  
  