Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable INFO open telemetry log from BigQuery #13131

Closed
potiuk opened this issue Dec 17, 2020 · 5 comments
Closed

Disable INFO open telemetry log from BigQuery #13131

potiuk opened this issue Dec 17, 2020 · 5 comments
Labels
good first issue kind:bug This is a clearly a bug

Comments

@potiuk
Copy link
Member

potiuk commented Dec 17, 2020

We started receiving this INFO log

{opentelemetry_tracing.py:29} INFO - This service is instrumented using OpenTelemetry. OpenTelemetry
 could not be imported; please add opentelemetry-api and opentelemetry-instrumentation
packages in order to get BigQuery Tracing data.

The log entry is very annoying and should be disabled by default.

@mik-laj
Copy link
Member

mik-laj commented Dec 18, 2020

@potiuk It seems to me that this problem should also be reported to the authors of the library. It is not a good idea to write logs while the module is importing..

@potiuk
Copy link
Member Author

potiuk commented Dec 18, 2020

@potiuk It seems to me that this problem should also be reported to the authors of the library. It is not a good idea to write logs while the module is importing..

For sure - will you ?

@potiuk
Copy link
Member Author

potiuk commented Dec 18, 2020

@potiuk It seems to me that this problem should also be reported to the authors of the library. It is not a good idea to write logs while the module is importing..

For sure - will you ?

But I thnk we need to disable it regardless in the default configuration.

@mik-laj
Copy link
Member

mik-laj commented Dec 18, 2020

For sure - will you ?

Of course. I'm already creating the ticket.

But I thnk we need to disable it regardless in the default configuration.

I think it's not a very critical bug for us to have to use workarounds on our side. If the authors of the library do not want to make changes to the library, we can try a workaround.

@mik-laj
Copy link
Member

mik-laj commented Jan 12, 2021

This is fixed in google-cloud-bigquery==2.6.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue kind:bug This is a clearly a bug
Projects
None yet
Development

No branches or pull requests

2 participants