Index of OpenTelemetry z/OS Attributes

z/OS-specific resource attributes for API ML provide essential mainframe context to your telemetry data, allowing you to correlate metrics, traces, and logs with specific system identifiers such as SMF IDs, Sysplex names, and LPARs. By providing z/OS platform context, mainframe performance data can be integrated into distributed observability backends.

z/OS Attribute Reference

The following attributes are captured during system discovery to describe the mainframe environment. For a full list of OTel z/OS attributes for z/OS integration, see the OpenTelemetry Semanic Conventions for z/OS software.

• zos.smf.id
  The System Management Facility (SMF) Identifier that uniquely identifies a z/OS system within a SYSPLEX. Configuration Source: System discovery

• zos.sysplex.name
  The name of the SYSPLEX to which the z/OS system belongs. Configuration Source: System discovery

• mainframe.lpar.name
  Name of the LPAR that hosts the z/OS system. Configuration Source: System discovery

note

The attributes zos.smf.id, zos.sysplex.name, and mainframe.lpar.name are automatically assigned through system discovery. These values can be overridden manually if required.

• For details about automated system discovery, see Configuring API ML Observability.
• For details about overriding these attributes, see Resource Attributes (Manual Overrides) in the article Advanced Configuration of API ML Observability.

• os.type
  The operating system type, set to zos. Configuration Source: Static

• os.version
  The version string of the operating system (e.g., the release returned by D IPLINFO). Configuration Source: System discovery

• process.command
  The command or JOB name used to launch the Zowe process. Configuration Source: System discovery

• process.pid
  The Process Identifier. For details about this property, see Process Attributes in the OpenTelemetry documentation. Configuration Source: System discovery

note

While the discovery process handles most identifiers automatically, you have the option to provide a manual override (for example, in shared environments where you wish to report a custom logical LPAR name). For details about overriding discovered attributes, see Advanced configuration of API ML Observability.