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

feat(api): expose alert groups in the API #1712

Closed
prymitive opened this issue Jan 16, 2019 · 3 comments
Closed

feat(api): expose alert groups in the API #1712

prymitive opened this issue Jan 16, 2019 · 3 comments

Comments

@prymitive
Copy link
Contributor

/api/v1/alerts/groups was removed via #1525 and there's no equivalent for /api/v2.
Having alerts accessible via the API with all the grouping information is useful if the intent is to consume alert information the same way it's grouped in notifications.
There is already some context given on #868 why would this be useful for alertmanager UI.
Due to flexibility of the routing logic it's quite complex to recreate same grouping outside of alertmanager, even if full routing config is known, hence the request to (re)add it to the API.

Related issues with additional context:
#868
prymitive/karma#115
#1694

@beorn7
Copy link
Member

beorn7 commented Feb 5, 2019

IMHO, this is a duplicate of #868. The latter should give you exactly what you need.

@prymitive
Copy link
Contributor Author

I think it's only a dup if #866 would be solved by adding a version of /api/v1/alerts/groups, that ticket talks also about the UI and I wasn't sure if there was any consensus yet of how is that going to be resolved and implemented, hence this ticket with a specific request.

If this suggestion is going to end up in alertmanager API (groupIDs field) and there will be a way to fetch group information (like the receiver it used and group_by labels) then I'm happy to close it as a dup as I think it would be all that I need.

@beorn7
Copy link
Member

beorn7 commented Feb 5, 2019

I think that's exactly what we need for #866.

The UI is entirely backed by API calls, so if AM's own UI can display the groups, the API has to support it, too.

@beorn7 beorn7 closed this as completed Feb 5, 2019
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

No branches or pull requests

2 participants