Skip to content

Fix pushgateway paths. - #97

Closed
butcher wants to merge 1 commit into
prometheus:masterfrom
butcher:fix-pushgateway-paths
Closed

Fix pushgateway paths.#97
butcher wants to merge 1 commit into
prometheus:masterfrom
butcher:fix-pushgateway-paths

Conversation

@butcher

@butcher butcher commented Dec 20, 2018

Copy link
Copy Markdown

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
Copy Markdown

Coverage Status

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

@coveralls

coveralls commented Dec 20, 2018

Copy link
Copy Markdown

Coverage Status

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

@butcher

butcher commented Dec 20, 2018

Copy link
Copy Markdown
Author

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
Copy Markdown
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

beorn7 commented Jan 25, 2019

Copy link
Copy Markdown
Contributor

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

4 participants