What logging possibilities does JobScheduler provide?

Introduction

The JobScheduler create number of different logs, to provide specific information about job, job chain, order, task and JobScheduler internal 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_DATA}/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. Install_VX.X.XXXX_timestamp.log
7. http.log
8. web_service,web_service_name.log

1. 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.

Each line of the scheduler.log contains in their columns the following information:

• Column 1: Starts with "." if demo version, Day of Month
• Column 2: Time (with ms)
• Column 3: application name (Windows) - empty otherwise
• Column 4: elapsed time in ms
• Column 5: Process ID, ".", Thread ID (hex)
• Column 6: Used memory in MB (Windows) - empty otherwise
• Column 7: Log text

2. scheduler-yyyy-mm-dd-hhmiss.log

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.

3. job.job_chain_name,job_name.log

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.

4. task.job_chain_location,job_chain_name,job_name.log

The task.job_chain_location,job_chain_name,job_name.log is created during individual tasks. The task log has most of the information about execution of instance of job i.e. parameters, std out, std error from the application.

5. order.job_chain_location,job_chain_name,order_id.log

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.

6. Install_VX.X.XXXX_timestamp.log

The install log has important information about JobScheduler installation. installation log is very important in case of JobScheduler has problem/error after fresh installation/update.

All the logs are saved in the database and can be accessed from the JOC and JID.