This article relates to the New Job Scheduling, which provides enhanced performance and support for different testing frameworks. For the original Job Scheduling, see Job Scheduling.
New Job Scheduling Service Logs
This article provides logging details for the New Job Scheduling services.
Supported log levels are TRACE, DEBUG, INFO, WARN, ERROR. Please note that TRACE captures everything. To change the log level for specific services, see Change Log Levels for New Job Scheduling Services.
| Service | Description | Log location | Default Logging level | Maximum file size | Maximum number of file |
|---|---|---|---|---|---|
| Job Scheduling Service |
Suite execution events are logged in Job Scheduling Service logs, in DEBUG log level. These include:
To get the full picture, search for the sandbox ID in the Quali Server and Execution Server logs. Each suite execution, job, test, sandbox and sandbox request has a unique ID. For example:
|
Console Logs directory under /JobSchedulingService (at least 2 files per day: one containing all the logs and the second one only errors) |
All logs: DEBUG Errors log: WARN |
All logs: 50 MB Error log: 10 MB |
All logs: 50 Error log: 10 |
| Test Execution Service | Job/test execution logs | Console | WARN | ||
| Test Discovery Service | Test repository connection logs | Console | WARN | ||
| Sandbox Service | Sandbox creation and management logs |
./ sandbox_service_logs |
WARN | 10 MB | 5 |
| Identity Service | General Identity Service logs - related to user activity in the New Job Scheduling | Logs are saved only to the console (docker logs) | WARN |
