Just double-checked: PromDash does still use the legacy API, unfortunately :(

So we can fix PromDash, keep the legacy API, or remove it and say it's ok to break PromDash (probably not so nice)...

Upgrading PromDash should be straightforward – mostly prefixing v1/.
Any Ruby volunteers?

@stuartnelson3 @grobie :)

Can one of you point me to an updated API doc? I'll do this ASAP and open a PR for your verification.

Great!

The API v1 docs are here.

Note that the URL change is the least part - the request/response has completely changed. But you should be able to copy the relevant bits from the Prometheus server's JS.

Who was the lazy person that updated the prometheus JS but not promdash..

So we can drop it? @stuartnelson3

Hey sitting in HBF, but promdash has been using the new API for a while. It
should be fine, but I haven't confirmed.

Am Donnerstag, 23. Juni 2016 schrieb Fabian Reinartz :

So we can drop it? @stuartnelson3 https://github.com/stuartnelson3

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1593 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABVVWP3KnkG7Ik-wcfw8ZlRzXvfbjeLsks5qOqH5gaJpZM4IPJVJ
.

Confirmed: prometheus-junkyard/promdash#484

Old API begone!

See comment on #1761 and see the PR #1601

Saw the PR – just wanted to be sure.
Seems we don't have versioned PromDash releases so it's fixed as soon as
it's in master?

On Thu, Jun 23, 2016 at 10:46 PM Björn Rabenstein notifications@github.com
wrote:

See comment on #1761 #1761
and see the PR #1601 #1601

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1593 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AEuA8o66BWngc62hY8ZmpOEmKM_K_DCmks5qOvCJgaJpZM4IPJVJ
.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.