Maksym Ochenashko

https://opentelemetry.io/docs/specs/semconv/database/database-metrics/ - there are official database semantic conventions, but they are still in the 'experimental' / 'development' state. But they should be marked stable, presumably this year. We can follow...

There is an experimental generation of instruments from semantic conventions: https://github.com/typelevel/otel4s/pull/764. If we merge it, we can use it to test the implementation.

> we should report the required attributes You can use OpenTelemetry [semantic conventions](https://github.com/open-telemetry/semantic-conventions) to generate specs and use them in tests to ensure all required attributes are in place. Here...

Not ideal, but you can do the following: ```scala OpenTelemetrySdk.autoConfigured[IO]( _.addExportersConfigurer(OtlpExportersAutoConfigure[IO]) .addTextMapPropagatorConfigurer(AutoConfigure.Named.const("myCustomPropagator", propagator)) ) ``` Then you can dynamically configure it: `export OTEL_PROPAGATORS=myCustomPropagator`. That doesn't improve usability, but it can...

Thanks for the contribution, looks good! A few minor changes, and we can merge the PR.

Thanks for the PR! I will review the changes this week.

Looks good overall, thanks! @NthPortal would you like to take a look?

Turns out the fs2-related warnings are already addressed: https://github.com/http4s/http4s/pull/7675. If we can merge #7675 first, I can rebase my PR afterward.

- [x] `[A] DBIO[A]#as(A): DBIO[A]` could be useful to: a shortcut for `.map(_ => a)`.

> `DBIO.defer[A](=>A): DBIO[A]` cats-effect [IO](https://github.com/typelevel/cats-effect/blob/1ba83f03445ff1cef778c3876486c5bb2b06350a/core/shared/src/main/scala/cats/effect/IO.scala#L1236-L1249) has these meanings for `delay` / `defer`: ```scala def delay[A](thunk: => A): IO[A] = ??? def defer[A](thunk: => IO[A]): IO[A] = delay(thunk).flatten ``` ZIO has...