It is still better to use something like spdlog or GLog (the library wrapped by Arrow's log) directly; or even if you use OpenTelemetry, we do not export the headers so you would need to depend on it explicitly (and OTel's logging is still under development in any case). And the Arrow exporter is there mostly for convenience when working with things like PyArrow/R; an application should directly configure OpenTelemetry itself.
But yes, Arrow's logging header is mostly there to support some warnings and runtime assertions. On Tue, Jul 5, 2022, at 22:37, Weston Pace wrote: > At the moment that log is used primarily for Arrow developers and is > not likely to be terribly useful beyond that. It is not, as far as I > know, very extensible. I think you can only configure it to log to > stderr or to a single file. However, it could be made extensible if > someone were motivated to do so. > > On the other hand, we are starting to add support for open telemetry. > That might be a better option. You will need to build Arrow with open > telemetry turned on (-DARROW_WITH_OPENTELEMETRY=ON) and then I don't > know if you have to do anything beyond that, other than configuring > OpenTelemetry globally. There is an environment variable > (ARROW_TRACING_BACKEND) which, when set, will lead Arrow to > configuring an exporter (e.g. you can set > ARROW_TRACING_BACKEND=ostream to dump to console) but I'm not sure you > need to do this if you configure the exporter in your parent > application. > > -Weston > > On Tue, Jul 5, 2022 at 1:06 PM José Almeida > <jose.alme...@simbioseventures.com> wrote: >> >> Hello guys, >> >> I am planning to add a log system into a c++ application that uses arrow >> flight sql, and I saw that arrows provides some logging methods >> (cpp/src/arrow/util/logging.h). I was wondering if there is any >> instruction/documentation related to this log, if there is a special >> configuration that I need to set. >> >> Thanks in advance, >> Best Regards >> Jose Almeida
