-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: VOLTHA v2.7
-
Fix Version/s: VOLTHA v2.8
-
Component/s: voltha-lib-go
-
Labels:None
-
Story Points:1
If both log-correlation and tracing is set to false, intercontainer message decode will output a warning message similar to the following to the log (output from pkg/kafka/kafka_inter_container_library.go (func: enrichContextWithSpan)
My assumption is that the no-op tracer or something similar to this is responsible.
{{ "level": "warn",}}
{{ "ts": "2021-02-18T18:43:19.220Z",}}
{{ "caller": "kafka/kafka_inter_container_library.go:827",}}
{{ "msg": "unable-to-deserialize-textmap-to-span",}}
{{ "instanceId": "voltha-voltha-rw-core-75459897b6-6zsbn",}}
{{ "textMap": {}}
{{ "uber-trace-id": "506d336dee479aa9:306a01214ae7db6b:0:0",}}
{{ "uberctx-op-name": "kafka-rpc-DeviceStateUpdate",}}
{{ "uberctx-rpc-span-name": "kafka-rpc-DeviceStateUpdate"}}
{{ },}}
{{ "error": "opentracing: SpanContext not found in Extract carrier",}}
{{ "stacktrace": "github.com/opencord/voltha-lib-..."}}
{{ },}}
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
25686,3 | [VOL-3855] Skip span generation if both tracing and log_correlation are disabled | master | voltha-lib-go | Status: MERGED | +2 | +1 |