[receiver/googlecloudpubsub] Turn noisy warn in reset metric (#37571) #37583
+450
−179
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 withlots 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