zio-telemetry
zio-telemetry copied to clipboard
zio
ZIO-powered OpenTelemetry library
In this version, no accessors will be required, just services that provide methods to perform these functions.
We are starting the context from a graphQL API ( or even earlier in case of distributed tracing, from the client). I didn't know how to pass the context to...
Currently all APIs accept a `toErrorStatus: PartialFunction[E, StatusCode]` and then set the `Span`'s `Status` like this: https://github.com/zio/zio-telemetry/blob/d59c6a7d4a7cdce95e30cbe9788fc27e1f13b794/opentelemetry/src/main/scala/zio/telemetry/opentelemetry/Tracing.scala#L46-L53 The default is `Map.empty`, meaning that for any defect or failure, we set...
- Allows integration with spans provided by opentelemetry java api
It would be nice to have some functions to manipulate the [OpenTelemetry Baggage](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/baggage/api.md).
Currently the opentracing module will report 2 traces for a single (1) request:  Here, the 'ROOT' span belonging only to 'zio-backend' was merely created when instantiating...
OpenTelemetry also allows to report metrics: - https://github.com/open-telemetry/opentelemetry-java/blob/master/QUICKSTART.md#metrics - https://github.com/open-telemetry/opentelemetry-specification/tree/master/specification/metrics zio-telemetry doesn't support these, but could potentially
PR to address the issue: https://github.com/zio/zio-telemetry/issues/585 # Changes - `opencencus` and `opentracing` have been migrated to module pattern 2.0 (`opentelemetry` was migrated in https://github.com/zio/zio-telemetry/pull/578) - Migrated examples - Added `Trace`...
I think there left a few things to improve to fully migrate to module pattern 2.0: - make in the next version all accessors deprecated in all modules - migrate...