Understanding Classic Request Resolver and Cache Span Disassociation
classic request resolver / cache span disassociation happening in RPC?
the http client/server post is next to the rpc span tree.
(code 422,
I would expect
and
(have to check what that dangling
, oh, auto instrumentation I guess
the http client/server post is next to the rpc span tree.
(code 422,
?action=GetMe is me experimenting with improving DX surrounding browser RPC http calls)I would expect
http.client POST to be inside Rpc.request GetMeand
Me.GetMe to be inside http.server POST(have to check what that dangling
POST span is exactly @opentelemetry/instrumentation-http)
