-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[receiver/googlecloudpubsub] noisy warning logs #37571
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/googlecloudpubsub
Describe the issue you're reporting
By default all of our deployed OTel collectors are running with logs configured to only emit warnings & errors. For a while now we've got recurring logs being emitted at a warning level for the googlepubsub receiver. Those are "internal" ones on how pubsub streaming pull works and should probably be emitted at debug level instead. The current warning log volume is about ~40k logs per day with around ~500 pods of those receivers deployed.
Example of such logs:
The text was updated successfully, but these errors were encountered: