* Generalize RPC semantic conventions to allow non-gRPC spans
* Add method name to attributes
* Require specifying `net.transport` for non-IP connections
* Do not require providing the port when it's not available
* Add package name to rpc.service and make it optional when not applicable or unknown
* Add note and example distinguishing the service.name resource attribute from rpc.service
* Distinguish RPC spans from HTTP spans
* Improve wording
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Improve wording
* Improve wording even more
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Clarify span name format
* Update changelog
* rpc.method: required -> recommended
* rpc.service: required -> recommended
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
I'm not sure what this should have to do with vendors, according to the examples, this would be the actual system names themselves. Otherwise the vendor for kafka would probably be "Apache", for example.
Armin Ruech