rabbitmq_shovel_prometheus: handle single atom shovel states #14480
+13
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Namely, 'starting'. Previously, a Prometheus scraping endpoint hit just at the right moment (when a shovel was in the 'starting' state) would produce a function_clause exception.
michaelklishin
deleted the
mk-rabbitmq-shovel-prometheus-should-handle-single-atom-shovel-states
branch
|
@Mergifyio backport |
❌ No backport have been created
GitHub error: |
michaelklishin
added a commit
that referenced
this pull request
Sep 2, 2025
…-should-handle-single-atom-shovel-states rabbitmq_shovel_prometheus: handle single atom shovel states (cherry picked from commit 232d968)
|
Manually backported to |
michaelklishin
added a commit
that referenced
this pull request
Sep 2, 2025
For 4.1.5: rabbitmq_shovel_prometheus: handle single atom shovel states (backport #14480)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Namely, 'starting'.
Previously, a Prometheus scraping endpoint hit
just at the right moment (when a shovel was
in the 'starting' state) would produce
a function_clause exception.