anchor.diff:  
   ### <a id="director-logs"></a>BOSH Director Logs ###
   
  -When you run a BOSH command using the [BOSH Command Line Interface (CLI)](http://www.google.com/url?q=http%3A%2F%2Fdocs-cloudfoundry-staging.cfapps.io%2Fbosh%2Fbosh-cli.html&sa=D&sntz=1&usg=AFQjCNGmisLsBEGpJ_nZjfPOVuxDyuvOiA), the Director stores all activities for the specific command in a task log. Review these logs when you experience an issue with a BOSH command. The Director stores logs in `/var/vcap/sys/log/director`.
  +When you run a BOSH command using the [BOSH Command Line Interface (CLI)](./bosh-cli.html), the Director stores all activities for the specific command in a task log. Review these logs when you experience an issue with a BOSH command. The Director stores logs in `/var/vcap/sys/log/director`.
   
   To access the Director logs:
   
   1. Run bosh tasks recent to find the task number of the failed command.
  -1. Run `bosh task <task_number>`. 
  +1. Run `bosh task <task_number>`.
   
       Example:
   
  
positive.code: ### <a id="jobs-services-logs"></a>Jobs Services Logs ###
  
  Active jobs on running VMs produce service logs. The BOSH deployment configuration determines the output location of a specific log. The creator of a release defines this location  in a config file stored in `release/jobs/<job_name>/templates/<config_file>`.
    
  If you use Cloud Foundry for deployment, it configures jobs to log to `/var/vcap/sys/log/<job_name>/<job_name>.log`.
  
  
  To review Service logs, run `bosh logs <job_name> <index>`.
  	
  ### <a id="database-services-logs"></a>Database Services Output Logs ###
  
  Database services that run within a job, such as PostgreSQL, can output logs into their own default locations. These default logging locations depend on the specific database services.
  
negative.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](./terminology.html).
  
  Monit detects errors and outputs useful information to its log. Use `tail` to examine the monit.log:
  
  