Setup: periodic service discovery rule - change from "first matching" to "all matching"

27 votes

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

Not planned Usability Suggested by: Lars Sörensen Upvoted: 12 Mar Comments: 3

Comments: 3