at the moment I try to setup import sources and sync rules in order to evaluate a new monitring landscape in our company.
I want to a achive that we can import from different sources to build up the monitoring spots.
To get there I need a lot of information - unfortunately these information are stored in multiple places.
Now - my problem is that I get my host / ip information from our old ldap (icinga1 / lconf) but for example when I try to source the os of these hosts I have to query a sql database with much more information I want.
To query the sql database isn’t a problem at all, but in this database there are hosts I do not want to monitor (external systems I can’t reach, dev-systems that should not be part of >this< monitoring, …).
Now I have set up the sql query as import source - no problem.
I can also import the os to all my hosts - no problem as well.
My problem is that the sync rule will also create new hosts out of the data it gets from the import source - but I dont want to add new hosts that the director doesn’t already know of.
Is there anything I can do to compare if this row of the import source that I (not me - the sync rule) am processing is already part of the known hosts and if not to blacklist this row?
Or is there anything I can do to exclude them while importing?
The expalined problem with the os is just an examlpe - I have multiple sources with different information.
As long as the new source has less information than the director - everything is fine.
For the other case I need a solution - and I realy need a solution and not just a workarround because I want to automate the hole monitoring setup in the future with just fetching the information I need and let the apply rules take care of the rest
BR and thanks in advance,