Db2 for z/OS traces (Datadog API integration)
Created , Updated
Below is a table describing the Datadog trace semantics that are utilized when z/IRIS streams Db2 for z/OS 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.
Db2 for z/OS tags via Datadog’s trace API
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 |
|---|---|---|
|
| Identifies the Db2 system for the request. |
|
| Identifies the Db2 accounting class performance data. |
|
| Identifies the Db2 accounting class performance data. |
|
|
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 . |
JDBC to Db2 for z/OS is not supported when streaming traces to Datadog via Datadog’s trace API or when JDBC applications are monitored by Datadog’s Agents.
service
The db2 service identifies the Db2 system.
Click to enlarge image
operation_name
operation_name is either set to Db2_Accounting or db2.call depending on integration mechanism used to access Db2.
Click to enlarge image
Operation names used by z/IRIS for Db2 spans
resource_name
Either identifies the Db2 location name where the db2.call operation was processed or contains Db2_Accounting.
Click to enlarge image
Resources listed for service:db2 and operation:db2.call