A swift OpenTelemetry client
This package includes several libraries. The
OpenTelemetryApi library includes protocols and no-op implementations that comprise the OpenTelemetry API following the specification. The
OpenTelemetrySdk library is the reference implementation of the API.
Libraries that produce telemetry data should only depend on
OpenTelemetryApi, and defer the choice of the SDK to the application developer. Applications may depend on
OpenTelemetrySdk or another package that implements the API.
opentelemetry-swift is designed for Swift 5. To depend on the opentelemetry-swift package, you need to declare your dependency in your
.package(url: "https://github.com/open-telemetry/opentelemetry-swift", from: "1.0.0"),
and to your application/library target, add
dependencies, e.g. like this:
.target(name: "ExampleTelemetryProducerApp", dependencies: ["OpenTelemetryApi"]),
.target(name: "ExampleApp", dependencies: ["OpenTelemetrySdk"]),
Currently Tracing, Metrics and Baggage API's and SDK are implemented, also OpenTracing shim, for compatibility with existing Opentracing code.
Implemented traces exporters: Stdout, Jaeger, Zipkin, Datadog and OpenTelemetry collector
Implemented metrics exporters: Prometheus, Datadog, and OpenTelemetry collector
The package includes some example projects with basic functionality:
Datadog Sample- Shows the Datadog exporter used with a Simple Exporter, showing how to configure for sending.
Logging Tracer- Simple api implementation of a Tracer that logs every api call
Network Tracer- Shows how to use the
URLSessionInstrumentationinstrumentation in your application
Simple Exporter- Shows the Jaeger an Stdout exporters in action using a MultiSpanExporter. Can be easily modified for other exporters
Prometheus Sample- Shows the Prometheus exporter reporting metrics to a Prometheus instance
OTLP Exporter- Shows the OTLP exporter reporting traces to Zipkin and metrics to a Prometheus via the otel-collector
|Last commit: 2 days ago|