h1. Introduction
The JobScheduler create number of different logs, to provide specific information about job, job chain, order, task and JobScheduler interanl operational itself.
The location of the the log files can vary as per as specific installation, but for default installation one can find the log files at ${SCHEDULER_HOME}/logs folder.

JobScheduler logs

1. scheduler.log
2. scheduler-yyyy-mm-dd-hhmiss.log
3. job.job_chain_name,job_name.log
4. task.job_chain_location,job_chain_name,job_name.log
5. order.job_chain_location,job_chain_name,order_id.log
6. http.log
7. web_service,web_service_name.log

scheduler.log

The scheduler.log is created during JobScheduler start up. Just before the JobScheduler startup JobScheduler copy the existing scheduler.log as scheduler-old.log, and create new 0 KB scheduler.log file. The scheduler.log has most of the information concerning internal working of the JobScheduler. The scheduler.log is create by all type JobScheduler instances i.e. standalone, cluster, agent, backup.

The scheduler-yyyy-mm-dd-hhmiss.log is created during JobScheduler and always create with a time stamp for archiving purposes. The scheduler-yyyy-mm-dd-hhmiss.log has information about process being executed by JobScheduler and other higher level information of JobScheduler operation. The log scheduler-yyyy-mm-dd-hhmiss.log can be configured to be rotate ( create new log with new time stamp) by an house keeping job. The log scheduler-yyyy-mm-dd-hhmiss.log is always stored on the file system.

The job.job_chain_name,job_name.log is created during execution of individual jobs. After job execution the log job.job_chain_name,job_name.log is also saved into the database.

The task.job_chain_location,job_chain_name,job_name.log is created during execution of individual task NOTE: one job can have multiple tasks. After task execution the log task.job_chain_location,job_chain_name,job_name.log is also saved into the database.

The order.job_chain_location,job_chain_name,order_id.log is create as order traverse from one node to another node. After order execution the order.job_chain_location,job_chain_name,order_id.log is also saved into the database.

All the logs saved in the database can be accessed from the JOC