birschick-bq opened a new issue, #4589: URL: https://github.com/apache/arrow-adbc/issues/4589
### What feature or improvement would you like to see? Currently, the **FlightSQL** go driver has instrumented `slog` messages (`DebugContext`, `InfoContext`, etc.) to log diagnostic messages. However, the `slog` messages are (currently) only routed to the `stderr` stream and are not persisted to the file system or available to OTel endpoints. I suggest that we port the `slog` messages to OTel tracing spans (`internal.StartSpan` / `internal.EndSpanWithError`) and events (`span.AddEvent` / `span.RecordError`) so that the information can be persisted to the file system or available to OTel endpoints. There are other alternatives, - add an `io.Writer` implementation to the `slog` streaming implementation - for file system persistence. - use the [OTel logging bridge](https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelslog) - for slog to OTel **logging**. However, I'm assuming we are content to standardize on using OTel **tracing**. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
