semantic-conventions/docs/rpc
Liudmila Molkova 17decc3f22
Add QUIC to the list of well known network transports (#1239)
Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com>
2024-07-15 09:04:16 -07:00
..
README.md [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
connect-rpc.md [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
grpc.md [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
json-rpc.md [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
rpc-metrics.md Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00
rpc-spans.md Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00

README.md

Semantic Conventions for RPC

Status: Experimental

This document defines semantic conventions for remote procedure calls (RPC) , also called "remote method invocations" (RMI).

Semantic conventions for RPC are defined for the following signals:

  • RPC Spans: Semantic Conventions for RPC client and server spans.
  • RPC Metrics: Semantic Conventions for RPC metrics.

Technology specific semantic conventions are defined for the following RPC systems:

  • Connect: Semantic Conventions for Connect RPC.
  • gRPC: Semantic Conventions for gRPC.
  • JSON-RPC: Semantic Conventions for JSON-RPC.

Specifications defined by maintainers of RPC systems:

  • gRPC: Semantic Conventions for gRPC.