Initial semantic conventions for mainframes

[rrschulze]

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:

1. mainframe: Adds single attribute to registry right now, (planned for platform-specific definitions moving forward)
2. zos: Adds z/OS related attributes and definition of z/OS system software resource (zos.software)

The PR is based on the input from the Mainframe SIG meetings to define initial semantic conventions for the mainframe.

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

• [x] CONTRIBUTING.md guidelines followed.
• [x] Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• [ ] schema-next.yaml updated with changes to existing conventions.

[kjsrobinson]

@rrschulze Can a new attribute be added for an SMF correlator, "zos.smf_correlator" or something similar?

[rrschulze]

@kjsrobinson We will discuss the use of zos.smf_correlator or zos.smf.correlation_id on the Mainframe SIG call. We may consider a more generic approach to correlate from one z/OS signal (e.g., trace) to another z/OS signal (e.g., metric from SMF). What is the relationship to metric exemplar. I suggest we will address the requirement with an additional PR (if required).

[github-actions[bot]]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[rrschulze]

thanks @lmolkova, appreciated!