Octez_telemetry.HTTP_client
Follow the OpenTelemetry specs for HTTP client, see https://opentelemetry.io/docs/specs/semconv/http/http-spans
val call_service :
Tezos_rpc_http.Media_type.t Tezos_base.TzPervasives.trace ->
?logger:Tezos_rpc_http_client_unix.RPC_client_unix.logger ->
?headers:(string * string) Tezos_base.TzPervasives.trace ->
base:Uri.t ->
([< Resto.meth ], unit, 'a, 'b, 'c, 'd) Tezos_rpc.Service.t ->
'a ->
'b ->
'c ->
'd Tezos_base.TzPervasives.tzresult Lwt.t
call_service media_types ?logger ?headers ~base service params query body
makes an HTTP request to the specified RPC service with OpenTelemetry tracing.
This function follows the OpenTelemetry semantic conventions for HTTP client spans, automatically setting appropriate attributes like HTTP method, URL, status code, etc. It also adds the header traceparent
to allow traces across different services.