task: Capture bridge message decoding failure details #240
Conversation
This file contains hidden or 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
There are infrequent fatal errors reported to the observability platform. The error reports contain very little details. This is an effort to uncover the origin of the failures.
dcalhoun
added
the
[Type] Task
jkmassel
approved these changes
Nov 25, 2025
dcalhoun
deleted the
task/capture-bridge-message-decoding-failure-details
branch
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.
There are infrequent fatal errors reported to the observability platform. The error reports contain very little details. This is an effort to uncover the origin of the failures.
What?
Capture and log additional details during bridge message decoding failures.
Why?
Close CMM-375. There are infrequent fatal errors reported to the observability platform. The error reports contain very little details. This is an effort to uncover the origin of the failures.
How?
Log the message type and body, in addition to the error.
Testing Instructions
N/A, no functional changes.
Accessibility Testing Instructions
N/A, no functional changes.
Screenshots or screencast
N/A, no functional changes.