Logs
Logs contain debug information that is used by the IBM Support to ensure they have all the information that they need to troubleshoot and repair tape library components quickly and reliably. These log files are not designed to be directly consumed by users.
There are three different types of log files delivered today: library service logs, snapshot logs, and drive service logs.
Library service logs are .zip files that are created by the user with the POST /v1/logs request. Each library service log is assigned a name in the format TS4500_LOG_<library-serial-number>_<date-time>.zipDiamondback_LOG_<library-serial-number>_<date-time>.zip. These logs are kept around but might be automatically deleted as new logs are created to save space. While library service logs are being created, a task is tracked for this action that can be monitored by using GET /v1/tasks .
Snapshot logs are .zip files that are created automatically when specific error conditions are encountered. Each snapshot log is assigned a name in the format TS4500_SS_<error-code>_<library-serial-number>_<date-time>.zipDiamondback_SS_<error-code>_<library-serial-number>_<date-time>.zip.
For Diamondback, the drive service logs are ZIP files that are exported from individual drives and created by the user by using the POST /v1/logs request. Each drive service log is assigned a name in the format Diamondback_DriveLogs_<drive-location>_<date-time>.zip. These logs are kept around but may be automatically deleted as new log files are exported to save space. The creation of a drive service log is almost immediate and not tracked via a task.
To view the attributes of specific logs of all types including their creation status, use the GET /v1/logs or GET /v1/logs/<filename> request.
Logs that are shown in this query can be exported if they are in the
complete
state by using the
GET/v1/logs/<filename>/export request.