Data accessible via API

[brancz]

Most of the data that is displayed via the web UI is also accessible via the API, however, some information is still missing. I would like to use this issue to collect the missing parts.

A possibly non exhaustive list I've been able to come up with that is still missing:

• runtime information shown on /status
• flags on /flags ✔️
• currently pending/firing alerts ✔️
• loaded config ✔️
• loaded rules ✔️

Anything I'm missing?

@beorn7 @brian-brazil @fabxc @juliusv

[beorn7]

It's basically everything under the Status tab, i.e. not only /status but also /flags, /config, /rules, /targets. Not sure if any of those can already be queried via the API.

[brian-brazil]

We have to be a little careful with some of those, as things like rule groups will likely change the formats even if the feature itself was backwards compatible.

[brancz]

@brian-brazil Agreed. For rules and config I was thinking for a start to really just expose the loaded string source.

@beorn7 /targets and /alertmanagers already exists on the API and was released in v1.5.0, but the others I agree with.

[mxinden]

I will start working on the /status/config endpoint exposing the currently loaded config as displayed in the UI.

[brian-brazil]

How much is left here?

[mxinden]

@brian-brazil In regards to exposing the status: Still working on #2711.

[mxinden]

How much is left here?

With #2711 merged, the loaded config can be retrieved via the API.

I will update the initial issue description. @brancz hope you don't mind.

I will see what I can do in regards to "currently pending/firing alerts" following up on #4012 and #3656.

[brancz]

@mxinden Go for it.

[mxinden]

How much is left here?

With #4318 merged, I updated the top level issue:

• currently pending/firing alerts ✔️
• loaded rules ✔️

[vn-ki]

Hi, I would like to work on this issue.

[vn-ki]

flags on /flags

If I'm not wrong, #3864 added this (v1/status/flags). This means only runtime stats are remaining.

[brancz]

Correct. Will mark flags as done.