milesbxf opened a new pull request, #3360: URL: https://github.com/apache/tinkerpop/pull/3360
## Why There's currently no way to instrument the HTTP transport layer in gremlin-go. Users who need connection pool monitoring, request tracing, or custom metrics have no extension point — the `http.Transport` is created internally and not exposed. This is particularly useful for diagnosing latency spikes caused by connection pool exhaustion under load. ## What Adds an `HTTPTransport http.RoundTripper` field to `ClientSettings` and `DriverRemoteConnectionSettings`. When set, the driver uses it directly instead of creating its own transport. When nil, behaviour is unchanged. ## Test plan - [x] New tests: custom transport is used, nil falls back to default, pool settings ignored with custom transport, wiring from both ClientSettings and DriverRemoteConnectionSettings - [x] Existing tests pass 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
