Make messaging context propagation requirements explicit #2750
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Georg Pirklbauer <georg.pirklbauer@dynatrace.com>
joaopgrassi
changed the title
blumamir
approved these changes
Aug 25, 2022
lmolkova
reviewed
Aug 25, 2022
lmolkova
approved these changes
Aug 25, 2022
dpauls
suggested changes
Aug 26, 2022
reyang
added
area:semantic-conventions
brunobat
reviewed
Sep 12, 2022
pyohannes
approved these changes
Sep 12, 2022
brunobat
approved these changes
Sep 14, 2022
dpauls
approved these changes
Sep 23, 2022
joaopgrassi
requested review from
brunobat,
pyohannes and
lmolkova
and removed request for
brunobat
brunobat
reviewed
Sep 26, 2022
carlosalberto
approved these changes
Sep 26, 2022
pyohannes
approved these changes
Sep 28, 2022
reyang
reviewed
Sep 30, 2022
Co-authored-by: Reiley Yang <reyang@microsoft.com>
This was referenced Oct 7, 2022
ppatierno
reviewed
Oct 24, 2022
| The consumer receives, processes, and settles a message. "Receiving" is the | ||
| process of obtaining a message from the intermediary, "processing" is the | ||
| process of acting on the information a message contains, "settling" is the | ||
| process of notifying an intermediary that a message was processed successfully. |
There was a problem hiding this comment.
Is "settling" really the notification about the message to be processed?
In general, the intermediary is only interested to know that the message was delivered to the consumer so on "receiving" it should be settled.
Processing the message is part of the "contract" between producer and consumer, so that by using a request-reply pattern and a "reply-to" address/queue/topic, the consumer can notify (via a new message) to the producer that the processing happened.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #2749
Changes
Related OTEP #205
This PR integrates the Context propagation section from the OTEP into the trace messaging semantic conventions.
I did some slight modification on the text, just to give more context on the "problem" and why this change is necessary. The core concept of the OTEP is still maintained of course.