Support more feature in the API

[lyrixx]

Right now, it's not easy to build a dashboard to expose all check status.
You could say I have to look at the status directly in consul. But I prefer
to read the data in consul-alerts because:

• I'm able to blacklist some checks
• consul-alerts do not use the exact check, but a "mean" of the last N secondes.

So It could be nice to more endpoints

• list of services with the "state"
• list of nodes with the "state"
• By able to filter by state on all endpoints
• ....

What do you think?

[darkcrux]

Yeah we also need something like this too.

probably also:

• list all checks and state
• by state, maybe also return if the check is enabled/disabled

[bcwilsondotcom]

One of the things I'm missing after migrating from Sensu to Consul is a nice ops focused dashboard. With Sensu I was using Uchiwa and I'd like to build something similar for Consul. I'm wondering if this is better handled in consul-alerts or consul itself though. We can already get a list of all checks and their status through the Consul API, right? So we'd query the Consul API for the check status, and make calls to the Consul-Alert API to disable alerts on checks. This keeps consul-alerts focused strictly on alerts and related configs. Thoughts?

[hunter]

We've been thinking along similar lines for building an ops dashboard. Using the consul APIs that already exist and using consul-alerts for the rest (adding anything missing we may need).

What do you see as the important features for inclusion in a Dashboard?

[lyrixx]

Actually, Consul-alerts bring use more feature that "just" consul:

• blacklist of node / service / checks
• retention to avoid flip/flap

This is why I think it's better to use consul-alert to build a dashboard. But I'm not really sure about that.

[lyrixx]

I don't need this feature anymore. Closing the issue.