-
Notifications
You must be signed in to change notification settings - Fork 61
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
Broker up/down status #12
Comments
Based on the Broker Status documented here: |
I think there is a simpler way: other exporters expose a metric like Related suggestions from the prometheus docs: If I find some time I will create a PR if that is OK. |
I was thinking to add a metric with the seconds since the last $SYS message. That can give rise an alarm if that value is higher that 60 seconds (or the $SYS update time configured in the broker). Also the up/down status detected by the status of the connection with the broker can be a good idea and with the other metric can detect both scenarios for broker error:
If you think it is a good idea I can work in a PR about it. |
Is there a way to determine if the broker is reachable? If my broker goes down the exporter will expose the last metrics it was able to scrape. Im currently using something like
to determine if there are any changes in the heap. But that is not very reliable so far.
I'm using the
0.4.0
tagged docker image of the exporter.The text was updated successfully, but these errors were encountered: