search

NETWAYS / icinga2-scom-connector

UNSUPPORTED - SCOM Alert connector for Icinga 2
GNU General Public License v2.0
2 stars 0 forks source link

Avoiding icinga2 reload #10

Closed swizzly closed 5 years ago

swizzly commented 5 years ago

Hi The plugin works fine. My only concern is, that the script has to be re-run every couple of minutes via systemd or crontab in order to receive the update from SCOM and icinga2 has to be also reloaded every time. In case of a larger environment it takes several seconds and causes CPU peaks. I'm wondering wheter there is a better way to inform Icinga2 about the changes without reloading the whole config. I know the modul writes new config files, that have to be re-read by icinga, but wouldn't it be more efficient to either write the changes into Icinga2 DB or send the changes to icinga2 via API? Cheers

swizzly commented 5 years ago

A workaround or alternative solution is mentioned in my comment: https://github.com/NETWAYS/icinga2-scom-connector/issues/11#issuecomment-461406348 With a slight modification of the code CSV output can be generated, that can be read by the Fileshipper Module and so it can be processed by the Director module. This way the configuration gets deployed on all the concerning icinga2 nodes and icinga2 does not have to be reloaded on a regular base via cronjob or whatsoever.