Update opentracing shim to map errors from logs

[codeboten]

As per spec:

The Add Event's name parameter MUST be the value with the event key in the pair set, or else fallback to use the log literal string.

If pair set contains a event=error entry, the values MUST be mapped from OpenTracing Log Fields to an Event with the conventions outlined in the Exception semantic conventions document:

open-telemetry/opentelemetry-specification#1563

[robertsben]

Hi, I'd opened this as a bug against the shim (#1870) having not seen this. Was wondering whether the intention was to address this in the shim, or whether you're looking to add it as a feature of the opentelemetry client (or collector) to translate the opentracing fields (error.kind->exception.type etc.) rather than directly emitting the opentelemetry ones (exception.type etc.)?

[srikanthccv]

This should be addressed in shim package.