swift-otel
swift-otel copied to clipboard
slashmo
OpenTelemetry client built for server-side Swift
Is recording should be: > IsRecording > > Returns true if this Span is recording information like events with the AddEvent operation, attributes using SetAttributes, status with SetStatus, etc. >...
As previously discussed in #23 I added a new job to the CI workflow file. Cannot verify if it works, as I cannot run the actions myself. @slashmo feel free...
Now that we're able to publish DocC-powered documentation on GitHub Pages and our current solution (`swift-doc`) was deprecated, we should definitely make use of it 📖
A probabilistic sampler (known as trace-id ratio based in OTel) samples spans with a given probability by comparing the random numbers contained in the trace-id to a max value derived...
To avoid not being aware of sampling at 100%, we should require users to always pass in a span when initializing `OTel`. To make things easier, we can expose the...
Passing custom headers alongside the export gRPC calls is necessary to support exporting directly to a supported backend using e.g. an API key. We should support the standard `OTEL_EXPORTER_OTLP_HEADERS` environment...
To directly export to supported backends via OTLP over gRPC, we need to offer the ability to configure the gRPC channel to use TLS. Currently, the exporter is hardcoded to...
Need to check what otel expects here but it tripped up some developers using swift-otel in CLI like situations so they didn't get their spans. Should we also flush during...
Users should be able to use Swift OTel to export all three signals via OTLP. We currently have Metrics and Distributed Tracing but still need to add swift-log exporting.