-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Add specific stream protocol counters to track protocol errors #3157
Conversation
This can now be rebased onto |
b956676
to
58e36b6
Compare
for changes occurring in 58e36b6
-define(PROTOCOL_COUNTERS, | ||
[ | ||
{ | ||
stream_error_stream_does_not_exist, ?STREAM_DOES_NOT_EXIST, counter, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these are counters, then Prometheus format requires them to end with _total
:
Note that an accumulating count has total as a suffix, in addition to the unit if applicable.
Apart from the above
@Gsantomaggio do you want to test After that, if you want Gabriele, we can add these to the new RabbitMQ-Streams dashboard 😉 |
Sure ! |
@gerhard Those test suites can't check for the new metrics, as they only show up when the stream protocol is used. There is a check for them on |
All looks good, starting QA in 3.9 LRE |
While this works, writing queries for these metrics is really difficult. This is what a single query looks like:
Could we capture the error type in a label, so that we would end up with metrics like these:
This would transform the above query into this:
As I mentioned above, while queries are difficult, this works and produces the following end-result: |
Having discussed this offline, it would be too difficult to capture the error types as labels. Leaving as is & merging. Thank you @dcorbacho! |
Add specific stream protocol counters to track protocol errors (cherry picked from commit ef4303a)
Backported to |
Types of Changes
Checklist
CONTRIBUTING.md
document