Skip to content
This repository has been archived by the owner on Jul 22, 2020. It is now read-only.

Support for both private and public endpoints for alertmanager #182

Closed
sylr opened this issue Sep 7, 2017 · 5 comments
Closed

Support for both private and public endpoints for alertmanager #182

sylr opened this issue Sep 7, 2017 · 5 comments
Assignees

Comments

@sylr
Copy link

sylr commented Sep 7, 2017

Hi,

Here my setup

  • Unsee in a docker container accessible from internet through oauth2_proxy.
  • Alertmanager in a docker container accessible from both a private network with no authentication and from internet trough oauth2_proxy.
  • Unsee talks to Alertmanager via the private network.

It works well but the silence feature unfortunately tries to use this private address of the Alertmanager declared in the conf.

It would be nice if we could define for each Alertmanagers a public ip that the silence feature would use.

Cheers.

@prymitive
Copy link
Contributor

I think I'll need to add a config file first for this, having complex syntax for flags / env variables isn't great.

@prymitive
Copy link
Contributor

#190 was closed by adding proxy support for client->unsee->alertmanager requests, does that help with this issue?

@sylr
Copy link
Author

sylr commented Jan 9, 2018

It should! I will test it! Thanks.

@prymitive prymitive removed this from the v0.9 milestone Jan 25, 2018
@prymitive
Copy link
Contributor

Can we close this now with proxy support in 0.9?

@sylr
Copy link
Author

sylr commented Feb 1, 2018

Yes! Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants