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

api: drop legacy API #1761

Merged
merged 1 commit into from
Jun 27, 2016
Merged

api: drop legacy API #1761

merged 1 commit into from
Jun 27, 2016

Conversation

fabxc
Copy link
Contributor

@fabxc fabxc commented Jun 23, 2016

Fixes #1593
Waiting for confirmation from @stuartnelson3 there.

@beorn7
Copy link
Member

beorn7 commented Jun 23, 2016

Isn't the Prometheus CLI using the legacy format?
And wasn't the reason to not just deprecate the Prometheus CLI that the Nagios plugin depends on it?
And wasn't the plan to build query functionality into promtool? That's in progress in #1753 .
But only once that's done, we can port the Nagios plugin and then drop the legacy API.

See also #1601 , the previous attempt to do this.

@beorn7 beorn7 mentioned this pull request Jun 23, 2016
@fabxc
Copy link
Contributor Author

fabxc commented Jun 24, 2016

Okay, can we merge this into master regardless?

@beorn7
Copy link
Member

beorn7 commented Jun 24, 2016

My impression was we do not want to break the Prometheus CLI before we have a replacement in promtool and ported the Nagios plugin to promtool.

@fabxc
Copy link
Contributor Author

fabxc commented Jun 24, 2016

It's in master and will be completed before the next release. Master is our development branch, breaking there is totally okay.

@beorn7
Copy link
Member

beorn7 commented Jun 24, 2016

Sure, but is not merging this PR blocking anything? If avoiding breakage has no cost, I'm for avoiding it.

I'd feel better if could shepherd #1753 into merging ASAP. @fabxc you already looked at it. How far away is it? I'm happy to port the Nagios plugin to promtool once the functionality is there.

@fabxc
Copy link
Contributor Author

fabxc commented Jun 24, 2016

It's having many things in the air.

Who knows how far, I made comments and am waiting for a response.
I also mentioned some concerns on how we handle time. So I ultimately expect promtool to not be stable (something we should make clear in our 1.0.0 guarantees).

Might be better to migrate prometheus_cli to APIv1 and keep it around for a bit.
Or... make the Nagios plugin talk the the API directly. Should be not too much overhead with curl and jq. How about that?

@beorn7
Copy link
Member

beorn7 commented Jun 24, 2016

Might be better to migrate prometheus_cli to APIv1 and keep it around for a bit.
Or... make the Nagios plugin talk the the API directly. Should be not too much overhead with curl and jq. How about that?

I'll look into that today.

@beorn7
Copy link
Member

beorn7 commented Jun 24, 2016

I'll look into that today.

Fniday is already over (in my timezone), but I'll try my best on Saturday...

@beorn7
Copy link
Member

beorn7 commented Jun 26, 2016

prometheus/nagios_plugins#8 is my attempt. I'll run it by @matthiasr to see if the escaping is right. (Worked for a number of cases I tried, but with shell, you never know for sure...)

@beorn7
Copy link
Member

beorn7 commented Jun 27, 2016

In any case, we know now the nagios plugin is totally doable with curl and jq, so I believe this can be merged now (assuming you got confirmation from @stuartnelson3 by now).

@stuartnelson3
Copy link
Contributor

PromDash no longer uses the legacy API. 👍 to this PR.

@fabxc fabxc merged commit 62af249 into master Jun 27, 2016
@fabxc fabxc deleted the fabxc-legacyapi branch June 27, 2016 12:26
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.

3 participants