birschick-bq commented on issue #4589:
URL: https://github.com/apache/arrow-adbc/issues/4589#issuecomment-5084692225
@lidavidm Thanks for the feedback.
- Using the **OTel** bridge for `slog` would be convenient so we wouldn't
have to port/rewrite any existing logging code. But I have a few concerns ...
- We'll need to add support for the OTel logging environment variable
like the
[exporter](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#exporter-selection)
(OTEL_LOGS_EXPORTER) and
[level](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#general-sdk-configuration)
(OTEL_LOG_LEVEL)
- Database/Connection options to set the exporter and level (and others
for file-based exporter).
- Endpoints or automated analysis of the data would now have to deal with
two different data models.
Do you have a description of what information is more appropriate for
logging than for tracing? Is it based on the "volume" of output? Or details?
Do you see that we might need to instrument two API calls for some
information, one for logging and one for 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]
