Skip to content

Separate messaging.system values from the spec#669

Closed
lmolkova wants to merge 2 commits intoopen-telemetry:mainfrom
lmolkova:messaging-system
Closed

Separate messaging.system values from the spec#669
lmolkova wants to merge 2 commits intoopen-telemetry:mainfrom
lmolkova:messaging-system

Conversation

@lmolkova
Copy link
Copy Markdown
Member

@lmolkova lmolkova commented Jan 25, 2024

Fixes #670

Changes

Please provide a brief description of the changes here.

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


**[7]:** If a custom value is used, it MUST be of low cardinality.

**[8]:** Messaging instrumentations MUST use applicable value from the [list of known messaging systems](/docs/messaging/README.md#technology-specific-semantic-conventions) when it is available. When instrumenting a new messaging system, instrumentation authors should document the new system name and add it to the [list](/docs/messaging/README.md#technology-specific-semantic-conventions).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New identifiers for messaging systems shouldn't be added to the README, but to the YAML files.

@lmolkova
Copy link
Copy Markdown
Member Author

closing in favor of #670 (comment)

@lmolkova lmolkova closed this Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Where/how *.system and similar should be defined

2 participants