search

NETWAYS / icinga2-scom-connector

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

scom_connector in icinga2 cluster #11

Closed swizzly closed 5 years ago

swizzly commented 5 years ago

Hi In an Icinga2 cluster, e.g. 2 Icinga2 Master Nodes where the SCOM Plugin is installed on only one of the nodes, the other node does not know about the SCOM objects. How could both icinga2 nodes get the same objects, I thought, that both Icinga2 nodes communicate with eachother and share the configs, or is it only in case if I use Director, or manage the objects via Icinga2 API? Do I need to install the SCOM plugin on both Icinga2 nodes? In this case both nodes would make the same query on the SCOM side and generate their configs independently.

lazyfrosch commented 5 years ago

This project was mainly a proof of concept, and is not really maintained or continued.

The idea is to refresh the config from time to time, when stuff in SCOM changes. Status updates should not require a reload.

swizzly commented 5 years ago

Ok, thanks for the reply. In the meanwhile I adapted the code to write CSV output, that can be read via Fileshipper in the Director modul, thus the config gets deployed to both master nodes, and also the Icinga config does not have to be reloaded. This way it gets a bit more robust. I wonder whether I could use the MSSQL Queries in Director directly ... ;-)