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

[Feature Request] use SIGNALILO_ICINGA_HOSTNAME from label value #14

Open
kubicgruenfeld opened this issue Mar 18, 2020 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@kubicgruenfeld
Copy link

Hey, first, thanks for this great piece of software!

We would like to use one Signalilo deployment for a few hosts in Icinga2, currently we only could deploy one Signalilo for one Icinga2 host which is, in our case, not feasible since we have roundabout 3k hosts in Icinga2.

My idea would be to take the icinga2 host from a label value and configure the api-user filters accordingly.

Is this a feature you also would like to implement anyway? I would like to do it myself and come up with a PR, but i have no experience in go programming for now.

@simu simu added the enhancement New feature or request label Mar 18, 2020
@simu
Copy link
Member

simu commented Mar 18, 2020

Hi, Thanks for reaching out!

For our internal use case, there is a one-to-one mapping from an OpenShift cluster Prometheus stack to a special Icinga2 host which only shows the Prometheus alerts for this particular cluster.

I think implementing this change should be fairly straightforward, even though there may be some spots in the code which assume that one Signalilo instance creates services on exactly one Icinga2 host.

A word of warning: while we'd happily review a PR, this is definitely not a use-case that has high priority for us internally, so it may be a while until we get around to trying to implement this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants