From ebcde82ea91fdf7e94b7858a51666fda0896b50a Mon Sep 17 00:00:00 2001 From: Nikita Salnikov-Tarnovski Date: Mon, 9 Nov 2020 18:48:44 +0200 Subject: [PATCH] Update status serialization for Zipkin (was: Remove mention of gRPC status codes) (#1186) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Christian Neumüller --- specification/trace/sdk_exporters/zipkin.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/specification/trace/sdk_exporters/zipkin.md b/specification/trace/sdk_exporters/zipkin.md index 5971648dac0..968809cff02 100644 --- a/specification/trace/sdk_exporters/zipkin.md +++ b/specification/trace/sdk_exporters/zipkin.md @@ -138,18 +138,16 @@ TBD: add examples ### Status -Span `Status` MUST be reported as a key-value pair in `tags` to Zipkin. +Span `Status` MUST be reported as a key-value pair in `tags` to Zipkin, unless it is `UNSET`. +In the latter case it MUST NOT be reported. The following table defines the OpenTelemetry `Status` to Zipkin `tags` mapping. | Status|Tag Key| Tag Value | |--|--|--| -|Code | `otel.status_code` | Name of the code, for example: `OK` | +|Code | `otel.status_code` | Name of the code, either `OK` or `ERROR`. MUST NOT be set if the code is `UNSET`. | |Message *(optional)* | `otel.status_description` | `{message}` | -The `otel.status_code` tag value MUST follow the [Standard GRPC Code -Names](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md). - ### Events OpenTelemetry `Event` has an optional `Attribute`(s) which is not supported by