-
Notifications
You must be signed in to change notification settings - Fork 9
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
Prometheus Never Prints the Buffer #70
Comments
I'll look right into it. |
Looks like a refactoring's gone wrong somewhere along the way. I've fixed the buffer issue and will be making sure that proper http requests are made. I'll publish a crate update right after that. |
@fralalonde +1 I just fixed this locally... I don't know what you had before but this is what I ended up with... Please note: the prometheus pushgateway is returning 400 w/ a body of
|
I just released v0.7.7, let me know how it runs... I'm happy to have someone helping me test Prometheus! |
Make that 0.7.8... |
@fralalonde One more issue if you didn't fix it: We should change the http call to I'll try out your new release! Thanks for the fix. I might have some docs coming your way. I've been playing around with using the Proxy => AtomicBucket => MultiOutput pipelines. The kicker here is you need to you use flush otherwise the Prometheus It took me a little while to figure out. Might as well pass it on. |
Btw, still seeing this error in the
See the PR here: |
I merged your PR, made some edits to the handbook regarding Proxy and published a new version. The new example you included is pretty nice too. I should document the other examples the same way. |
This looks good! Thanks for the quick turnaround. |
Been scratching my head at why I'm not seeing metrics sent to Prometheus.
Looks like this
strbuf
is created for the metrics but never passed to `self.flush_innerhttps://github.com/fralalonde/dipstick/blob/master/src/output/prometheus.rs#L104
https://github.com/fralalonde/dipstick/blob/master/src/output/prometheus.rs#L137
I'm not familiar with the inner workings on this library to submit a patch just yet. If I can figure it out, I'll update this Issue.
The text was updated successfully, but these errors were encountered: