anchor.diff:      </pre>
   
   1. Run `bosh logs <job_name> <index> --agent`.
  -	
  +
       If you receive notification that a job will not start, use `tail` to review the log for that Agent for possible causes:
   
       <pre class="terminal">
  
positive.code: 
  ### <a id="monit-logs"></a>BOSH Monit Logs ###
  
  The BOSH agent uses monit to start, restart, and stop services included in each [job template](http://www.google.com/url?q=http%3A%2F%2Fdocs.cloudfoundry.org%2Fbosh%2Fterminology.html%23job&sa=D&sntz=1&usg=AFQjCNGG2o3rRTQmaCmwL-1dl4I-Sa97eQ).
  
  Monit detects errors and outputs useful information to its log. Use `tail` to examine the monit.log:
  
  
negative.code: ---
  
  This topic describes different types of logs for BOSH jobs and errands and how you access and view them.
  For general information on logging, refer to the [Cloud Foundry Logging](../running/managing-cf/logging.html) topic.
  
  ## <a id="jobs-logging"></a>Jobs Logging ##
  
  You can access logs by two methods:
  
   * Using the `bosh ssh` command to access the log location.
   * Using the log-specific BOSH command to generate a config file to standard output.
  
  The following sections describe the logs that contain job information.
  
  ### <a id="agent-logs"></a>BOSH Agent Logs ###
  
  Agent logs contain configuration and runtime information from an Agent running on a specific VM. Review these logs if a VM fails.
  The Agent stores logs in `/var/vcap/bosh/log`.
  
  To review an Agent log:
  
  1. Run `bosh vms` to display a table of that provides an overview of VMs in the deployment.
  
  	Use this table to identify the Job/Index associated with a specific VM.
  
      For example:
  
      <pre class="terminal">
      $ bosh vms
      Deployment `wordpress'
  