Skip to content
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 pushgateway paths. #97

Closed
wants to merge 1 commit into from

Conversation

butcher
Copy link

@butcher butcher commented Dec 20, 2018

Hi @grobie, please review this fix, cause currently ruby_client is broken.

Since pushgateway released v0.7.0 deprecated /metrics/jobs/ interface
was removed and only singularized /metrics/job/ support now.

See pushgateway release notes and PR that removes deprecated API

Since pushgateway released v0.7.0 deprecated `/metrics/jobs/` interface
was removed and only singularized `/metrics/job/` supports now.

Signed-off-by: Pavel Nikitin <daddybutcher@gmail.com>
@butcher butcher force-pushed the fix-pushgateway-paths branch from 6f6f7ca to c2c4d59 Compare December 20, 2018 12:47
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c2c4d59 on butcher:fix-pushgateway-paths into 300de85 on prometheus:master.

@coveralls
Copy link

coveralls commented Dec 20, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling c2c4d59 on butcher:fix-pushgateway-paths into 300de85 on prometheus:master.

@butcher
Copy link
Author

butcher commented Dec 20, 2018

Looks like rake can not be installed for any 1.x ruby version. Since this commit was merged.
@grobie it is time to remove 1.9.3 from .travis.yml
That is the reason why travis CI check not passed.

@dmagliola
Copy link
Collaborator

it is time to remove 1.9.3 from .travis.yml

Agreed.
These are two commits from another PR with a little bit of housekeeping in them, including this.
I think they'd be valuable as independent PRs:

08d2a73
7ff1eaa

This was referenced Jan 21, 2019
@beorn7
Copy link
Member

beorn7 commented Jan 25, 2019

Apologies. This slipped through the radar of the maintainers. The problem has been fixed in #102 by now. Closing this. Thanks for your contribution anyway.

@beorn7 beorn7 closed this Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants