z/OS Work traces with OpenTelemetry
Created: | Updated:
Refer to z/OS Work observability for details about monitoring batch jobs and address spaces.
z/IRIS creates traces that comply with the OpenTelemetry’s OTLP specification and enriches traces with attributes that contain metadata about the mainframe system, processing, performance and resource consumption. Refer to z/OS Work trace attributes with OpenTelemetry for more information.
Services
z/OS Work traces can be grouped by service.name, the value of which, refers to the work type identifier derived from SMF30WID. Most z/OS Work span names, refer to the name of the Unit of Work (UOW), referred to as jobname in this documentation, and is derived from SMF30JBN.
Traces
TSO
LOGON
Logon traces signal that a user logged onto a z/OS system and provides the timestamp at which the logon occurred. Attributes describe the user as well as the system the user logged onto.
Click to enlarge image
Example of a logon trace
LOGOFF
Logoff traces indicate that a user’s z/OS session has ended and provides the total duration of the user’s session. Attributes provide user information, the resource consumption and information about the relevant z/OS system. When a user's session ends with an error or terminates abnormally, an error message will be provided.
Click to enlarge image
Example of a logoff trace
JES2: jobname
Signals one of the following:
Start of a batch job
Signals when the processing of a job has begun. Attributes provide information about the user and the relevant z/OS system. These traces have a duration of 0ms.
Click to enlarge image
Example of a job started trace
End of a step in a job
Signals that a step in a job has completed and provides the total duration of the step. Attributes provide the resource consumption of the step, information about the job, associated user and system. These traces can be selected by searching for zos.job.step.ended=true under service.name=JES2 and can be filtered according to a step name using zos.job.step_name. If the step ends abnormally, an error message will also be provided.
Click to enlarge image
Example of a job step ended trace
End of a batch job
Signals that a job has completed and provides the total duration of the job. Attributes provide the resource consumption of the job, information about the job, associated user and z/OS system. These traces can be selected by searching for zos.job.ended=true and can be filtered by job identifiers using service.instance.id. If the step ends abnormally, an error message will also be provided.
Click to enlarge image
Example of a job ended trace
STC: jobname
STC traces signal one of the following:
Started task initiated
Signals that processing has begun for a started task and provides the time at which processing began. Attributes provide information about the associated user and system.
Click to enlarge image
Example of an initiated started task trace
Started task ended
Signals that a started task has ended and provide the total duration of the started task. Attributes provide the information about its resource consumption and performance, as well as the associated user and z/OS system. These traces can be selected by searching for zos.job.ended=true under service.name=STC. If the step ends abnormally, an error message will also be provided.
Click to enlarge image
Example of a trace showing that a started task ended
OMVS: jobname
OMVS traces signal that one of the following:
OMVS process spawned
Signals that an OMVS process spawned and provides the start timestamp of the OMVS process. Attributes provide information about the associated user and z/OS system.
Click to enlarge image
Example of a spawned OMVS process trace
OMVS process ended
Signals that a spawned OMVS process has ended and provides the total duration of the OMVS process. Attributes provide information about its resource consumption and system performance, as well as information about the associated user and z/OS system. These traces can be selected by searching for zos.job.ended=true under service.name=OMVS. If the step ends abnormally, an error message will also be provided.
Click to enlarge image
Example of an OMVS process ended trace
Errors
Error messages
Refer to z/OS Work trace attributes | Error-messages for more information about z/OS Work error messages.
>> z/OS Work events with OpenTelemetry