Jonny Rhea 19f5fe079b rpc, internal/telemetry: trace JSON-RPC response writes (#35049) ... The per-call SERVER span ended inside `handleCall()`, so the JSON-RPC response write happened after the span closed. For large responses like `engine_getBlobsV*`, that write time was missing from traces. - Extend the SERVER span past `writeJSON`. - For batches, add a top-level `jsonrpc.batch` SERVER span (with `rpc.batch.size`) covering the whole batch including `callBuffer.write`. - Add `rpc.writeJSON` span around the non-batch response write. - Add `rpc.writeJSONBatch` span around the batch response write. - Add `rpc.httpWrite` span around the actual HTTP write, separating JSON encoding from network write. - Add additional telemetry helpers. --------- Co-authored-by: Felix Lange <fjl@twurst.com>		2026-06-02 14:13:06 +02:00
..
tracesetup	internal/telemetry: add gRPC transport for OTLP trace export (#33941)	2026-04-21 14:48:21 +02:00
telemetry.go	rpc, internal/telemetry: trace JSON-RPC response writes (#35049)	2026-06-02 14:13:06 +02:00
telemetry_test.go	internal/telemetry: don't create internal spans without parents (#33780)	2026-02-17 14:12:42 +01:00