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

Data accessible via API #2467

Closed
brancz opened this issue Mar 3, 2017 · 14 comments
Closed

Data accessible via API #2467

brancz opened this issue Mar 3, 2017 · 14 comments

Comments

@brancz
Copy link
Member

brancz commented Mar 3, 2017

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
Copy link
Member

beorn7 commented Mar 3, 2017

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
Copy link
Contributor

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
Copy link
Member Author

brancz commented Mar 3, 2017

@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
Copy link
Member

mxinden commented May 11, 2017

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

@brian-brazil
Copy link
Contributor

How much is left here?

@mxinden
Copy link
Member

mxinden commented Jul 14, 2017

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

@mxinden
Copy link
Member

mxinden commented Jun 18, 2018

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
Copy link
Member Author

brancz commented Jun 18, 2018

@mxinden Go for it.

@mxinden
Copy link
Member

mxinden commented Aug 13, 2018

How much is left here?

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

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

@vn-ki
Copy link
Contributor

vn-ki commented Jan 31, 2019

Hi, I would like to work on this issue.

@vn-ki
Copy link
Contributor

vn-ki commented Jan 31, 2019

flags on /flags

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

@brancz
Copy link
Member Author

brancz commented Jan 31, 2019

Correct. Will mark flags as done.

@roidelapluie
Copy link
Member

I think this can be closed.

@codesome
Copy link
Member

I can see runtime information at /status but I also see an open PR for this #5165 which tries to add some stuff which is already present. Not sure what else is left to be added. Closing this for now and can be reopened if needed.

@lock lock bot locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants