Skip to content
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

Re-introduce namespace to describe the original destination #156

Conversation

joaopgrassi
Copy link
Member

Continuing #100, closes #123

As discussed and agreed in the messaging SIG meeting on 2022/06/29 (meeting notes) we are re-introducing the name and anonymous attributes under the messaging.destination_publish namespace.

cc @pyohannes @dpauls @lmolkova

PS: I re-added some text from the old PR and re-worked it a bit. Let me know if you think it makes sense!

@joaopgrassi joaopgrassi requested review from a team June 30, 2023 15:14
Copy link
Contributor

@lmolkova lmolkova left a comment

Choose a reason for hiding this comment

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

LGTM!

@joaopgrassi joaopgrassi force-pushed the feat/destination_publish_return branch 3 times, most recently from 0f0fea7 to 739974c Compare July 7, 2023 07:50
@joaopgrassi joaopgrassi force-pushed the feat/destination_publish_return branch from 739974c to 6ce2a16 Compare July 14, 2023 08:03
@joaopgrassi
Copy link
Member Author

Hi @open-telemetry/specs-semconv-maintainers this is ready to merge. We have an agreement between the messaging SIG.

@arminru arminru merged commit 6c0c6a0 into open-telemetry:main Aug 7, 2023
@arminru arminru deleted the feat/destination_publish_return branch August 7, 2023 16:58
bryce-b pushed a commit to bryce-b/semantic-conventions that referenced this pull request Aug 8, 2023
rapphil pushed a commit to rapphil/semantic-conventions that referenced this pull request Aug 14, 2023
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.

Messaging: How to describe original destination messages were published from
6 participants