fix: add structured logging for streamable HTTP transport errors - #332
Open
samithreddychinni wants to merge 1 commit into
Open
Conversation
samithreddychinni
requested a review
from abhishekpanditofficial
as a code owner
August 8, 2026 11:49
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
adds structured logging for Streamable HTTP request failures by routing them through existing logger and including the request method, path, and error message as metadata. Direct StreamableHttpTransport usage still falls back to console.error, and failed POST and GET requests continue to return a JSON-RPC 500 response. I also added regression coverage for both request methods and documented the default logging behavior. Closes #17.