* Remove rpc.jsonrpc.method, clarify rpc.method instead.
* Add PR#.
* Clarify client side code.namespace/function.
* Use "ref" instead of "constraint: any_of".
This should be changed back once
https://github.com/open-telemetry/build-tools/issues/33
is resolved & the updated build tools available.
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
* Updating gRPC status semantic conventions
Since the simplification of trace status codes,
they no longer align with gRPC.
Clarifying the expected status code field for gRPC, as
well as the mappings between gRPC and OpenTelemetry status.
* Adding changelog entry
* Addressing feedback
Clarifying that gRPC spans should include the status code number,
rather than leave it ambiguous.
Adding gRPC semantic conventions in the yaml files to reflect these
changes.
* adding trailing whitespace
* Apply suggestions from code review
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* addressing feedback
Ran table-generation to ensure that semantic conventions are added.
Removed tags for rpc.grpc yaml for now (not explicitly used).
* Update specification/trace/semantic_conventions/rpc.md
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
* Addressing feedback
re-generating TOC with markdown-toc
There was a conflict with sub-headings matching the same string. As such
qualified all headings.
* Switching gRPC status_code type to enum
gRPC's status_code code is better expressed as an enum.
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Christian Neumüller