Add Metrics sections to RPC system-specific conventions

.chloggen/copilot_add-metrics-section-to-rpc-docs.yaml

@@ -0,0 +1,17 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: rpc
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add Metrics sections to JSON-RPC, gRPC, and Connect RPC system-specific conventions
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [3319, 3320]

docs/rpc/connect-rpc.md

@@ -6,11 +6,22 @@ linkTitle: Connect
 
 **Status**: [Development][DocumentStatus]
 
+<!-- toc -->
+
+- [Spans](#spans)
+  - [Client](#client)
+  - [Server](#server)
+- [Metrics](#metrics)
+
+<!-- tocstop -->
+
 The Semantic Conventions for [Connect](https://connectrpc.com/) extend and override the [RPC spans](rpc-spans.md) and [RPC metrics](rpc-metrics.md) Semantic Conventions
 that describe common RPC operations attributes in addition to the Semantic Conventions
 described on this page.
 
-## Client Span
+## Spans
+
+### Client
 
 <!-- semconv span.rpc.connect_rpc.call.client -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -147,7 +158,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-## Server Span
+### Server
 
 <!-- semconv span.rpc.connect_rpc.call.server -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -297,4 +308,11 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
+## Metrics
+
+Connect RPC instrumentations SHOULD collect metrics according to the general
+[Semantic Conventions for RPC Metrics](/docs/rpc/rpc-metrics.md).
+
+`rpc.system.name` MUST be set to `"connectrpc"`.
+
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status

docs/rpc/grpc.md

@@ -6,11 +6,22 @@ linkTitle: gRPC
 
 **Status**: [Development][DocumentStatus]
 
+<!-- toc -->
+
+- [Spans](#spans)
+  - [Client](#client)
+  - [Server](#server)
+- [Metrics](#metrics)
+
+<!-- tocstop -->
+
 The Semantic Conventions for [gRPC](https://grpc.io/) extend and override the [RPC spans](rpc-spans.md) and [RPC metrics](rpc-metrics.md) Semantic Conventions
 that describe common RPC operations attributes in addition to the Semantic Conventions
 described on this page.
 
-## Client Span
+## Spans
+
+### Client
 
 <!-- semconv span.rpc.grpc.call.client -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -148,7 +159,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-## Server Span
+### Server
 
 <!-- semconv span.rpc.grpc.call.server -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -299,4 +310,11 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
+## Metrics
+
+gRPC instrumentations SHOULD collect metrics according to the general
+[Semantic Conventions for RPC Metrics](/docs/rpc/rpc-metrics.md).
+
+`rpc.system.name` MUST be set to `"grpc"`.
+
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status

docs/rpc/json-rpc.md

@@ -6,11 +6,22 @@ linkTitle: JSON-RPC
 
 **Status**: [Development][DocumentStatus]
 
+<!-- toc -->
+
+- [Spans](#spans)
+  - [Client](#client)
+  - [Server](#server)
+- [Metrics](#metrics)
+
+<!-- tocstop -->
+
 The Semantic Conventions for [JSON-RPC](https://www.jsonrpc.org/) extend and override the [RPC spans](rpc-spans.md) and [RPC metrics](rpc-metrics.md) Semantic Conventions
 that describe common RPC operations attributes in addition to the Semantic Conventions
 described on this page.
 
-## Client Span
+## Spans
+
+### Client
 
 <!-- semconv span.rpc.jsonrpc.call.client -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -119,7 +130,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-## Server Span
+### Server
 
 <!-- semconv span.rpc.jsonrpc.call.server -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
@@ -234,4 +245,11 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
+## Metrics
+
+JSON-RPC instrumentations SHOULD collect metrics according to the general
+[Semantic Conventions for RPC Metrics](/docs/rpc/rpc-metrics.md).
+
+`rpc.system.name` MUST be set to `"jsonrpc"`.
+
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status