Would've been cool to be able to trace down from application-level sql execution to postgres-level index-scans table-scans and maybe even full query plan.
This turned out to be the opposite
(note: there is a C++ client[1], although they mention that support for C is not currently[2] a goal of the project -- and I couldn't find any C implementations elsewhere)
[1] - https://github.com/open-telemetry/opentelemetry-cpp.git/
[2] - https://github.com/open-telemetry/opentelemetry-cpp/tree/db6...
A quote from their v1.9.0 release notes[1]:
> We fully support Prometheus & OpenMetrics and we are also shipping experimental OpenTelemetry metrics support (spoiler: traces will come shortly!).
(I've no affiliation with Fluent nor particular knowledge of observability, so if anyone's interested in these findings, take them with a grain of salt :))
[1] - https://docs.fluentbit.io/manual/development/library_api
Would capturing and sending OpenTelemetry metrics from the PostgreSQL codebase using the Fluent Bit C library + the OT plugin require a separate process on the host at runtime?
(in other words, does the library ship those events to a collector/transmitter process, or is everything handled in-process?)
[1] - https://github.com/fluent/fluent-bit/blob/master/tests/runti...