-
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
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 1, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 1, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 1, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 1, 2025
Fixed by #37583 |
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 5, 2025
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Feb 5, 2025
mx-psi
pushed a commit
that referenced
this issue
Feb 5, 2025
…#37583) #### Description The receiver uses the Google Cloud Pub/Sub StreamingPull API and keeps a open connection. The Pub/Sub servers recurrently close the connection after a time period to avoid a long-running sticky connection. Before the receiver logged `warn` log lines everytime this happened. These log lines are moved to debug so that fleets with lots of collectors with the receiver don't span logs at warn level. To keep track of the resets, whenever a connection reset happens a `otelcol_receiver_googlecloudpubsub_stream_restarts` metric is increased by one. #### Link to tracking issue Fixes 37571 #### Documentation Documentation is auto generated for the metric
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: