open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
semantic-conventions/docs/rpc
History
Liudmila Molkova a8535bdeb3
Make url.scheme opt in for HTTP client metrics and make server.port required (#459) 
Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com>
 		2023-10-31 10:59:22 +01:00
..
README.md Bump to latest specification version. (#379) 2023-10-11 09:29:44 -04:00
connect-rpc.md Moved rpc attributes to the registry (#395) 2023-10-23 15:52:46 +02:00
grpc.md Moved rpc attributes to the registry (#395) 2023-10-23 15:52:46 +02:00
json-rpc.md Moved rpc attributes to the registry (#395) 2023-10-23 15:52:46 +02:00
rpc-metrics.md Remove outdated section in rpc-metrics.md that no longer applies (#447) 2023-10-25 23:11:44 +02:00
rpc-spans.md Make url.scheme opt in for HTTP client metrics and make server.port required (#459) 2023-10-31 10:59:22 +01: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.