census: Trace annotation for reporting inbound message sizes #9944
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.
This PR uses OpenCensus Annotation to report message size [bytes] for inbound/received messages in traces.
addMessageEvent
API which is currently used expects both uncompressed and compressed message (optional) sizes to be reported at the same. Since decompression for messages happens at a later point in time, reporting compressed message as is and reporting uncompressed size as-1
renders the size as 0 bytes received in cloud tracing front end.As a workaround, we add two annotations for each received message:
This PR also removes
addMessageEvents
a flag introduced in PR #9485 to temporarily suppress message events for gcp-observabilityCC @ejona86 @sanjaypujare