semantic-conventions/docs/rpc
Preston Vasquez 5e932efbfc
[chore] allow category-specific values in OTEL_SEMCONV_STABILITY_OPT_IN (#2158)
2025-04-22 18:05:57 +00:00
..
README.md Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
connect-rpc.md [chore] Update spec repo links to v1.44.0 (#2118) 2025-04-15 22:19:29 +00:00
grpc.md [chore] Update spec repo links to v1.44.0 (#2118) 2025-04-15 22:19:29 +00:00
json-rpc.md Set span kind on span definitions or change ambiguous spans to attribute groups (#1890) 2025-02-12 10:45:31 -08:00
rpc-metrics.md [chore] allow category-specific values in OTEL_SEMCONV_STABILITY_OPT_IN (#2158) 2025-04-22 18:05:57 +00:00
rpc-spans.md [chore] allow category-specific values in OTEL_SEMCONV_STABILITY_OPT_IN (#2158) 2025-04-22 18:05:57 +00:00

README.md

Semantic conventions for RPC

Status: Development

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.