Disable INFO open telemetry log from BigQuery
See original GitHub issueWe 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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Disabling Cloud Logging | Resource Manager Documentation
In the list of policies that appears, click Disable Cloud Logging. The Disable Cloud Logging policy uses the constraints/gcp.disableCloudLogging ID. The Policy ...
Read more >subject:"\[GitHub\] \[airflow\] yougyoung94 ... - The Mail Archive
... a comment on issue #13131: Disable INFO open telemetry log from BigQuery ... To respond to the message, please log on to...
Read more >OpenTelemetry - Apache Camel
Sets exclude pattern(s) that will disable tracing for Camel messages that matches the pattern. The content is a Set<String> where the key is...
Read more >opentelemetry-instrumentation - PyPI
Instrumentation Tools & Auto Instrumentation for OpenTelemetry Python. ... For more info about opentelemetry-distro check here
Read more >Registry | OpenTelemetry
This exporter supports sending tracing, metrics, and logging data to ... is used to prevent out of memory situations on the collector. processor...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in
google-cloud-bigquery==2.6.2
.Of course. I’m already creating the ticket.
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.