-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fix prometheus endpoints #628
Conversation
Possible to add specs for the metrics (i.e. integration style, read the prometheus end-point and verify the numbers)? We have a simple parser in Crystal https://github.com/84codes/prometheus.cr |
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.
LGTM 👍
Agree with @jage , would be great to verify with a spec or two!
Seems like the prometheus parser is not used in any of our projects, has no starts of forks.. @jage is the intention to maintain it? |
No, provided as-is. There's another non-public parser available, but not sure what's the best fit here. |
… parser to spec_helper
754968e
to
546045d
Compare
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.
LGTM!
(but run crystal tool format
)
WHAT is this pull request doing?
Fixes the
PrometheusController
,Previously the iterator
vhosts
fromtarget_vhosts()
was misused, resulting in the value being 0 for many metrics.Now we let
vhosts
be an array, instead of an iterator. This allows us to iterate over it many times, as we do inregister_routes
.Also: Adds a
type
to the metrics that were missing it, so that datadog is able to scrape everything.HOW can this pull request be tested?
accumulate some queues, messages, exchanges etc. and check the endpoint at
http://localhost:15672/metrics