RPC calls
If you are using automatic instrumentation, RPC call spans are created and attributes filled automatically. If using manual instrumentation, follow the conventions described below:
Naming convention
The span name has the <package>.<service>/<method> format, e.g., grpc.users.UserService/GetUserInfo. If the package name is missing or unknown, the <package>. part is omitted. For more information, see the RPC span naming specification.
Attributes
|
Attribute |
Description |
|
|
RPC system type: |
|
|
Service name: |
|
|
Method name: |
|
|
gRPC status code: |
|
|
Host name or IP address of the target server |
|
|
Target server port |
|
|
Client IP address |
|
|
Client port |
For a full list of attributes, see the OpenTelemetry specification for RPC spans.
Example
order-service requests user data from user-service over gRPC:
|
Attribute |
Client span |
Server span |
|
Name |
|
|
|
Kind |
|
|
|
Status |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
— |
|
|
|
— |
|
|
— |
|
|
|
— |
|