Setup: periodic service discovery rule - change from "first matching" to "all matching"
If you have several periodic service discovery Rules that perform different discovery tasks and they match the same Host only one of the Rule is executed. Because of the of the "first matching rule defines the parameter" Rule all other discovery tasks are ignored.
Example:
Rule 1 - add chronyd Service on all Linux Server
Rule 2 - adds new Interface Services on all Server
Rule 3 - add new/remove vanished Application Checks on all Application Server
Result: If it's a Linux Application Server only one of this Rules will be executed depending on the first match. In the end you will never know exactly which rule will be executed on which Host.
Therefor the behavior should be changed from "first matching rule" to "all matching rule" so that each of the discovery tasks will be executed independently.
Ps. the bulk discovery can't do the Job because it has no conditions and can't be sheduled
Comments: 3
-
02 Jul, '22
Marsellus WallaceBeware this should better use some kind of "first matching rule sets parameter" Like machanism instead of "match all", because the rules also set intervals and the service can always only have just 1 interval... ;-)
-
12 Jul, '22
Lars SörensenI think that the periodic service discovery should not be treated like normal rules, they should be treated more like list of single individual recurring tasks or cron jobs that are executed independently.
-
18 Oct, '23
Martin Hirschvogel AdminThis is technically not possible and there are no ways to make this happen in a feasible way. Thus, we will not do this. Sorry!