-
Notifications
You must be signed in to change notification settings - Fork 10
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
ICINGA2 issue with Zone and Satellite #25
Comments
If I understand it correctly, the problem is you create the host in a different zone than master. Sync is only top-down in the hierarchy so from master to satellite. |
Thanks for this fast answer, indeed I didn't thought that I could workaround this by defining the zone in another icinga Host template. |
I am still not very familiar with the UI part, so perhaps @timogoebel can help here. |
I also find this: https://github.com/theforeman/foreman_monitoring/blob/master/app/models/concerns/foreman_monitoring/host_extensions.rb |
I don't think i have the skills to create a PR :/ maybe by adding something like this |
Hi,
I setup a monitoring proxy to target a icinga2 master that belongs to "ZoneA" when I deploy a host, he is created in "ZoneA" in icinga2 and visible in the GUI (icingaweb).
For a different network zone I use a Icinga2 satellite that belongs to "ZoneB".
When I deploy a host in this ZoneB, thru the previously mention monitoring proxy, foreman seems to assign the ZoneA.
Therefore I create another monitoring proxy pointing to my Icinga2 SAtellite in ZoneB, here i can see that the host is created, i can even see that he is checked (thru the foreman sync status) but when I look at my icingaweb2 the host does not show up...
According to the following issue it might be normal: Icinga/icinga2#6052
Maybe I miss something obvious,... maybe we could pass the zone as a parameter from foreman? (i'm keen to make a PR if someone show me where it should be added, I'm not a ruby fan :p )
Maybe it is related to my icingaweb2 config?
Any help would be really appreciate
The text was updated successfully, but these errors were encountered: