OpenTelemetry

Currently the following OpenTelemetry features are supported:

metrics using OpenTelemetryMetricsBackend, wrapping any other backend
tracing using OpenTelemetryTracingZioBackend, wrapping any ZIO2 backend
tracing using trace4cats, wrapping a cats-effect backend

Metrics

The backend depends only on opentelemetry-api. To use add the following dependency to your project:

"com.softwaremill.sttp.client3" %% "opentelemetry-metrics-backend" % "3.10.1"

Then an instance can be obtained as follows:

import scala.concurrent.Future
import sttp.client3._
import sttp.client3.opentelemetry._
import io.opentelemetry.api.OpenTelemetry

// any effect and capabilities are supported
val sttpBackend: SttpBackend[Future, Any] = ???
val openTelemetry: OpenTelemetry = ???

OpenTelemetryMetricsBackend(sttpBackend, openTelemetry)

All counters have provided default names, but the names can be customized by setting correct parameters in constructor:

import scala.concurrent.Future
import sttp.client3._
import sttp.client3.opentelemetry._
import io.opentelemetry.api.OpenTelemetry

val sttpBackend: SttpBackend[Future, Any] = ???
val openTelemetry: OpenTelemetry = ???

OpenTelemetryMetricsBackend(
  sttpBackend,
  openTelemetry,
  responseToSuccessCounterMapper = _ => Some(CollectorConfig("my_custom_counter_name"))
)

Tracing (ZIO)

To use, add the following dependency to your project:

"com.softwaremill.sttp.client3" %% "opentelemetry-tracing-zio-backend" % "3.10.1"  // for ZIO 2.x

This backend depends on zio-opentelemetry.

The OpenTelemetry backend wraps a Task based ZIO backend. In order to do that, you need to provide the wrapper with a Tracing from zio-telemetry.

Here’s how you construct ZioTelemetryOpenTelemetryBackend. I would recommend wrapping this is in ZLayer

import sttp.client3._
import zio._
import zio.telemetry.opentelemetry._
import sttp.client3.opentelemetry.zio._

val zioBackend: SttpBackend[Task, Any] = ???
val tracing: Tracing = ???

OpenTelemetryTracingZioBackend(zioBackend, tracing)

By default, the span is named after the HTTP method (e.g “HTTP POST”) as recommended by OpenTelemetry for HTTP clients, and the http method, url and response status codes are set as span attributes. You can override these defaults by supplying a custom OpenTelemetryZioTracer.

Tracing (cats-effect)

The trace4cats project includes sttp-client integration.