anchor.diff:  	</tbody>
   </table>
   
  -## <a id='format'></a> About Log File Formats and Third-Party Log Management Software  ##
  +## <a id='format'></a> The Syslog Protocol and How Syslog Messages are Transmitted  ##
   
   Loggregator formats logging data that it sends to third-party services according to [RFC 5424](http://tools.ietf.org/html/rfc5424), titled *The Syslog Protocol*.
   Logs viewed in the CLI are not in syslog format.
  
positive.code: In this case, you create a user-provided service instance using the `cups` command with the `-l` option and the syslog URL you obtained earlier.
  See [User-Provided Services] (./user-provided.html#user-cups).
  
  Now the service instance and the syslog drain exist, but the service install still needs to be bound to the app.
  
  ### <a id='bind'></a>Bind the service instance to the application ###
  
  See [Binding User-Provided Service Instances to Applications](user-provided.html#cups-example).
  
  ## <a id='types'></a> Types of Logs ##
  
  
negative.code: 
  ## <a id='cli'></a>Preparation: Viewing Logs in the Command Line Interface ##
  
  The `cf logs` command enables you to view logs in the CLI.
  You can view all the logging information that Loggregator has or receives, or filter it using shell commands.
  The log output examples below are edited for brevity.
  
  **Note**: The filtering examples use the Linux `grep` command.
  Depending on your operating system and shell, you may need to use a different command or syntax.
  
  1. `cf logs <app_name>` displays all of the logging information that Loggregator receives in (almost) real time.
  
  	<pre class="terminal">
  		$ cf logs nifty-gui
  