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

Remove outdated section in rpc-metrics.md that no longer applies (#447)

This commit is contained in:
Trask Stalnaker 2023-10-25 14:11:44 -07:00 committed by GitHub
parent 384edab510
commit b8a493b915
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/rpc/rpc-metrics.md
View File

@ -271,10 +271,6 @@ different processes could be listening on TCP port 12345 and UDP port 12345.
| `connect_rpc` | Connect RPC | | `connect_rpc` | Connect RPC |
<!-- endsemconv --> <!-- endsemconv -->
To avoid high cardinality, implementations should prefer the most stable of `server.address` or
`server.socket.address`, depending on expected deployment profile. For many cloud applications, this is likely
`server.address` as names can be recycled even across re-instantiation of a server with a different `ip`.
For client-side metrics `server.port` is required if the connection is IP-based and the port is available (it describes the server port they are connecting to). For client-side metrics `server.port` is required if the connection is IP-based and the port is available (it describes the server port they are connecting to).
For server-side spans `server.port` is optional (it describes the port the client is connecting from). For server-side spans `server.port` is optional (it describes the port the client is connecting from).