Created: | Updated:

Below is a table describing the Datadog trace semantics that are utilized when z/IRIS streams CICS Transaction Spans 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.

>> CICS Transaction Observability

CICS Transaction span semantics

The table below shows how z/IRIS configures Datadog-specific tags for CICS transaction spans streamed using Datadog’s trace API.

Datadog Tag

Value

Description

service

cics

Identifies CICS as a mainframe service used by a request.

operation_name

The value is derived from the value available in the z/IRIS tag zos.cics.transaction.id .

Identifies the CICS transaction used by a request processed on mainframe.

See CICS Transaction Spans for more information about the zos.cics.transaction.id tag.

resource_name

zos.cics.transaction.id

Same as above.

host

host.name

Identifies the host system.

Values set in the host tag have no effect in the Datadog back-end. Users should integrate z/IRIS traces using OpenTelemetry to be able to list mainframe LPARs by host.name.

>> Complete list of CICS Transaction span tags

service:cics

CICS transactions spans are logically combined under the service name "cics". Each span represents a unit of work or transaction executed in CICS.

Click to enlarge image

Example of filtering traces using service in Datadog

operation_name

The zos.cics.transaction.id identifies the operation performed by CICS.

Click to enlarge image

Example of searching for CICS traces using operation_name in Datadog

resource_name

The zos.cics.transaction.id identifies the transactions as a resource used by a CICS request.

Click to enlarge image

CICS transactions listed as resources within the Service Dashboard in Datadog