feat(ai-proxy): distinguish MCP connection errors from configuration errors in logs #1440
+99
−10
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.

Summary
Warninstead ofErrorErrorThis reduces log noise when MCP servers are temporarily unavailable, which is a common scenario when customers configure MCP servers but don't remove them when they go down.
Connection error patterns detected:
ECONNREFUSED,ENOTFOUND,ETIMEDOUT,ECONNRESET,ENETUNREACH,EHOSTUNREACH,EPIPE,ECONNABORTEDfetch failed,socket hang up,network errorMCP error -32000(ConnectionClosed),MCP error -32001(RequestTimeout)spawn ENOENT,spawn EACCESTest plan
🤖 Generated with Claude Code