-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial semantic conventions for mainframes #1741
base: main
Are you sure you want to change the base?
Conversation
Removed trailing spaces.
Removed trailing spaces.
Removed trailing spaces.
Fixed EOF
Added space after comma
Added empty line at end of file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For CICS transactions the group id assigned during transaction attach time may also be useful for root cause analysis across various tools/reports.
Unless there is an IMS equivalent, perhaps a tpc.cics attribute would be suitable:
IBM Customer Information Control System (CICS) Attributes
This group defines attributes for IBM Customer Information Control System (CICS) for z/OS
Attribute | Type | Description | Examples | Stability |
---|---|---|---|---|
tps.cics.group_id |
string | Describes the group ID assigned at transaction attach time and can be used to correlate the transactions that CICS® runs for the same incoming work request | 0 ; 1 |
Fixes #1687
Changes
This PR lays out the initial structure of the semantic conventions for mainframes.
The PR adds the following new components to the semantic conventions:
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 and to determine how mainframe concepts will be integrated in the semantic conventions. Basing on the generic TPS, we aim to finalize the span definitions for CICS and IMS.
Note
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]