Initial definition of a Transaction Processing System (TPS) #1898
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1687
Changes
The PR is based on the input from the Mainframe SIG meetings and is intended to have the discussion to complete the definition of a generic Transaction Processing System. Basing on the generic TPS, we aim to finalize the span definitions for CICS and IMS.
The PR adds the following new components to the semantic conventions:
tps: Introduces new (generic) Transaction Processing System (TPS), an initial set of attributes and defines TPS spans extending the HTTP and RPC servers spans, and uses them for initial definition of server spans for the TPS CICS and IMS available on the mainframe.
ibm: Introduces ibm as name space to represent specific attributes of systems like ibm.cics and ibm.ims (aiming to align with guidance for system names described in #1708
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]