Area(s)
area:new
Is your change request related to a problem? Please describe.
For a consistent representation of mainframe telemetry using OpenTelemetry, Semantic Conventions supporting the platform are essential. The Mainframe SIG has made progress in agreeing first proposals for mapping mainframe concepts into the OpenTelemetry Semantic Conventions, and would like to now bring forward for further refinement with the Semantic Conventions SIG.
Describe the solution you'd like
As an initial input, add new model enhancements for the following mainframe aspects:
- z/OS attributes
- Registry:
zos.*zos.smf.id - 4-char Systems Measurement Facility (SMF) ID commonly used for system identificationzos.sysplex.name - The name of the SYSPLEX to which the system belongs too.
- Transaction Processing Systems (TPS) resources and spans
- For CICS and IMS.
- Alignment with non-mainframe transaction processing systems required
- Registry:
tps.*
tps.system - Type of Transaction Processing Systemtps.region.id - Runtime environment within the Transaction Processing Systemtps.transaction.id - ID of the transaction initiated by a user or system requesttps.transaction.owner - ID of the user owning the transactiontps.task.id - ID of the task created to run the transactiontps.program.name - Program name executed by the tasktps.unit_of_work.id - Unit of work executed by the program
- Mainframe attributes
- Registry:
mainframe.*mainframe.lpar.name - The name of the Logical Partition (LPAR) on which the system runs on.
Over time, we aim to extend the content under mainframe.*, zos.* and tps.* with metrics and events, and additional attributes. In addition, we look at adding definitions extending the name space system.* and adding enhancements for virtualisation.*.
Describe alternatives you've considered
Alternative for tps: Include under name space zos, e.g. such as zos.cics.* or zos.ims.*
Alternatives mainframe: Include concepts under hw and host namespaces, and potentially a new namespace for io to represent the I/O subsystems.
Additional context
No response
Area(s)
area:new
Is your change request related to a problem? Please describe.
For a consistent representation of mainframe telemetry using OpenTelemetry, Semantic Conventions supporting the platform are essential. The Mainframe SIG has made progress in agreeing first proposals for mapping mainframe concepts into the OpenTelemetry Semantic Conventions, and would like to now bring forward for further refinement with the Semantic Conventions SIG.
Describe the solution you'd like
As an initial input, add new model enhancements for the following mainframe aspects:
zos.*zos.smf.id- 4-char Systems Measurement Facility (SMF) ID commonly used for system identificationzos.sysplex.name- The name of the SYSPLEX to which the system belongs too.tps.*tps.system- Type of Transaction Processing Systemtps.region.id- Runtime environment within the Transaction Processing Systemtps.transaction.id- ID of the transaction initiated by a user or system requesttps.transaction.owner- ID of the user owning the transactiontps.task.id- ID of the task created to run the transactiontps.program.name- Program name executed by the tasktps.unit_of_work.id- Unit of work executed by the programmainframe.*mainframe.lpar.name- The name of the Logical Partition (LPAR) on which the system runs on.Over time, we aim to extend the content under
mainframe.*,zos.*andtps.*with metrics and events, and additional attributes. In addition, we look at adding definitions extending the name spacesystem.*and adding enhancements forvirtualisation.*.Describe alternatives you've considered
Alternative for
tps: Include under name spacezos, e.g. such aszos.cics.*orzos.ims.*Alternatives
mainframe: Include concepts underhwandhostnamespaces, and potentially a new namespace forioto represent the I/O subsystems.Additional context
No response