Skip to main content
Skip table of contents

z/OS Connect traces (Datadog API integration)

Created , Updated


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

>> z/OS Connect Observability


z/OS Connect tags via Datadog’s trace API

z/OS Connect parent span

The table below shows how z/IRIS configures Datadog-specific tags for MQ for z/OS traces streamed using Datadog’s trace API. Refer to z/OS Connect spans for a complete list of tags.

Datadog Tag

Value

Notes

service

The value is derived from the value contained in the tag:

zos.connect.service.name from z/OS Connect spans

Identifies the target service of the REST API request processed on a z/OS Connect.

Example: /employeeList

operation_name

Constant:

zosconnect.request

The operation is always set to “zosconnect.request”

resource_name

Concatenation of http.method and http.target

Identifies the REST API method and target processed on a z/OS Connect server.

Example: POST /customer/add

host

host.name

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 .

service

The service tag identifies service endpoints called by REST API requests processed on z/OS Connect servers.

Example: service:employeeList

Click to enlarge image

employeeList Service Page in Datadog

operation_name:zosconnect.request

operation_name is always set to zosconnect.request for z/OS Connect spans.

Click to enlarge image

Example of selecting ‘Operation’ belonging to Services in Datadog

Click to enlarge image

Trace explorer query for all traces with zosconnect.request operations.

resource_name

z/IRIS combines the REST API http.method and http.target to create a resource_name that identifies the type of REST API request processed by a z/OS Connect server.

Click to enlarge image

z/OS Connect Resources listed within the Service Dashboard in Datadog


System-Of-Record (SOR) child span

Datadog Tag

Value

Notes

service

The value is derived from the value of service.name of the SOR.

See SOR service name mapping for possible values.

operation_name

Possible values are:

  • wola.call

  • db2.call

  • ims.call

  • cics.call

  • mq.call

Identifies the operation executed by z/OS Connect on behalf of the SOR.

resource

Values are derived from the value contained in the z/IRIS tag zos.connect.sor.identifier.

Identifies the resource used by the SOR. See SOR Span tags for more details.

host

host.name

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 SOR span tags

service

All SOR services represent the subsystem on the mainframe that is the service provider for incoming REST API requests from z/OS Connect servers. See SOR service name mapping for more examples of possible values.

Example of traces filtered by the wola service

operation_name

This field represents the logical unit of work performed by the SOR. For example wola.call or db2.call

Click to enlarge image

Example of a wola.call SOR operation linked to a zosconenct.request parent span

resource

Identifies the resource utilized by the SOR. Example: resource:CICSREG1 will provide all z/OS connect traces where the CICS region named CICSREG1 was used to process the REST API request.

Click to enlarge image

Example of a batch job SOR resource linked to a zosconnect.request

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.