You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imported the command definitions et al. into the Director according to ICINGA.rst -> All Plugins, I also followed
If you did not name your master zone master during the initial icinga2 node wizard, find and replace "zone": "master" with "zone": "your-master-zone-name" in the icingaweb2-module-director-basket.json file.
When trying to apply these service templates on a test host, icinga2 refused the configuration:
critical/config: Error: Validation failed for object 'lx-test-01.example.com!Load' of type 'Service'; Attribute 'command_endpoint': Command endpoint must be in zone 'example-masters' or in a direct child zone thereof.
At some point remembering that there are special zones for Director configuration deployment. So I set there "global-templates" and turned out to be happy. Next I tried with an empty zone configuration, so it ended up in the "director-global" zone, but still all fine.
Can you please improve the documentation accordingly?
Steps to reproduce - Plugin call
N/A
Steps to reproduce - Data
No response
Environment
icinga2 r2.14.0-1
Icinga Web 2 2.11.4
Director 1.10.2
OS: RHEL 8.8
Plugin Version
2023051201
Python version
No response
List of Python modules
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
This issue respects the following points:
Which variant of the Monitoring Plugins do you use?
Bug description
We have a 3-tier Icinga2 monitoring setup using satellites according to the Distributed Monitoring documentation.
I imported the command definitions et al. into the Director according to ICINGA.rst -> All Plugins, I also followed
When trying to apply these service templates on a test host, icinga2 refused the configuration:
At some point remembering that there are special zones for Director configuration deployment. So I set there "global-templates" and turned out to be happy. Next I tried with an empty zone configuration, so it ended up in the "director-global" zone, but still all fine.
Can you please improve the documentation accordingly?
Steps to reproduce - Plugin call
N/A
Steps to reproduce - Data
No response
Environment
icinga2 r2.14.0-1
Icinga Web 2 2.11.4
Director 1.10.2
OS: RHEL 8.8
Plugin Version
2023051201
Python version
No response
List of Python modules
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: