Moritz Lang
Moritz Lang
We should update the documentation to include a section about automatic context propagation, and remove any mention of the soon to be removed `LoggingContext`.
We might want to consider offering an API to rename an already started span. This is [part of the OTel spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#updatename) but comes with a disadvantage for sampling. ### Use-Case:...
[The OTel specification states](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#record-exception) that Span’s `recordException` (in our case `recordError`) should take an additional argument to optionally specify `SpanAttributes`. These additional attributes (in case of OTel) are then merged...
OpenTelemetry defines a `Resource` as part of its spec: https://github.com/open-telemetry/opentelemetry-specification/blob/v0.7.0/specification/resource/sdk.md > Resource captures information about the entity for which telemetry is recorded. For example, metrics exposed by a Kubernetes container...
Lots has happened in the OpenTelemetry specification since we defined our top-level Tracing API. Now that their [Trace API froze](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/api.md), we should go over it once again to check if...
### Preface I noticed that while [AWS is Otel-compatible](https://aws.amazon.com/otel/?otel-blogs.sort-by=item.additionalFields.createdDate&otel-blogs.sort-order=desc), it does not (yet?) support W3C TraceContext for propagation, which is the default used in Otel. Instead, to support it in...
In some cases it might make sense to split a single `Baggage` value into several `Logger.Metadata` values. E.g. a `SpanContext` which contains things like `traceID`, `spanID`, and `traceFlags` might want...
The constants for using OTel spec compliant span attributes should instead life in a separate swift-distributed-tracing-extras package.
Are there any plans on supporting Swift 3.1 & 4.0 in the future? I'd also be happy to submit a PR to update it.