z/OS Work traces (Datadog API integration)
Created: | Updated:
Below is a table describing the Datadog trace semantics that are utilized when z/IRIS streams z/OS Work traces using the Datadog API.
To find out more about integrating z/IRIS with Datadog using the Datadog API, refer to Traces integration using Datadog API.
Services
service values | Span naming convention | Notes |
|---|---|---|
| ||
| ||
| ||
| ||
|
Trace
TSO
tso.logon
Logon traces signal that a user logged onto a z/OS system and provide the timestamp at which the logon occurred. Tags contain the user as well as the system the user logged onto.
Click to enlarge image
Example of a logon trace
tso.logoff
Logoff traces indicate that a user’s z/OS session has ended and provides the total duration of the user’s session. Tags 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
jes2.job
JES2 traces signals one of the following:
Start of a batch job
Signals when the processing of a job has begun. Tags provide information about the user and the relevant z/OS system. These traces have a duration of 0 ms.
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. Tags provide the resource consumption of the step, information about the job, associated user and system. These traces can be selected by searching for service: jes2, zos.job.step.ended: true 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. Tags 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 job ends abnormally, an error message will also be provided.
Click to enlarge image
Example of a job ended trace
STC
stc.procedure
STC traces signals one of the following:
Started task initiated
Signals that processing has begun for a started task and provides the time at which processing began. Tags 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. Tags 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 service: stc, zos.job.ended: true. If the job ends abnormally, an error message will also be provided.
Click to enlarge image
Example of a trace showing that a started task ended
OMVS
omvs.process
OMVS traces signals one of the following:
OMVS process spawned
Signals that an OMVS process spawned and provides the start timestamp of the OMVS process. Tags contain 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. Tags 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 service: omvs, zos.job.ended: true. If the step ends abnormally, an error message will also be provided.
Click to enlarge image
Example of an OMVS process ended trace
Error messages
z/OS units-of-work that terminate with a non-zero return code will contain error messages. Refer to z/OS Work trace attributes with OpenTelemetry | Error-messages to find out more about these types of errors.