Opentelemetry-js: Default log level

[naseemkullah]

Hello I recently instrumented a process that makes many queries to 3rd party apis. I used the http and dns plugins. My log sink is being flooded with noise. What is the suggested approach? I am using default sampling rate and Jaeger exporter.

[naseemkullah]

I've adjusted the tracer's logLevel: opentelemetry.LogLevel.ERROR as per the getting started guide.

[naseemkullah]

Should we maybe make the default log level info ?

[mayurkale22]

The current default LogLevel is DEBUG and default Logger is ConsoleLogger, maybe we can change ConsoleLogger -> NoopLogger or DEBUG -> ERROR.

[naseemkullah]

Is there documentation about the use case between ConsoleLogger and NoopLogger? I take it the name should be self explanatory but I am still unsure.

Furthermore, would there be any benefit to have structured logging for error logs in production in particular, and if so would it be alright to implement this via pino?

[vmarchaud]

@naseemkullah
ConsoleLogger logs to the console and NoopLogger doesn't do anything, i don't think we have specific documentation yet though.

There are always benefit having more implementation of our API to better suit end-users way of doing so i guess we could have a dedicated package PinoLogger which implement structured logging.

[naseemkullah]

Thanks for explaining @vmarchaud , a JsonLogger might be nice, good to know we can add it in the future.

[dyladan]

Per SIG this will be changed to INFO when we go from alpha to beta. add examples for override