> Quoting Gregory Sloop <[email protected]>: > > > See comments following... > > > > mic> At the beginning of the ***Targets***, just after the statement > > mic> beginning with "The following variables can be set in this section:", > > mic> the "alerts" are described as: > > > > mic> A comma separated list of alerts to check for this target. The alerts > > mic> have to be setup in the Alerts section. Alerts are inherited by child > > mic> nodes. Use an empty alerts definition to remove inherited alerts from > > mic> the current target and its children. > > > > mic> Then in the Level 1 section that follows a few sentences later, it is > > mic> written for alerts that: > > > > mic> Comma separated list of alert names > > > > mic> This variable inherits its value from the parent section if > > mic> nothing is specified here. > > > > mic> So, the first statement says that "use an empty alert definition to > > mic> remove inherited alerts from the current target and its children". > > mic> Then in the section for configured targets it says: "This variable > > mic> inherits its value from the parent section if nothing is specified > > mic> here". These two statements clash, only one can be true. So, what is > > mic> the true statement? > > > > [Provided I understand your question...] > > I think what it's saying is: > > > > If you leave a child section without any *explicitly* defined alerts, it > > will get the alerts from its parent. > > > > If you want to cancel/remove an alert for a child section, then define an > > "empty" alert with the same name in the child and you don't get that > > alert from the parent. If there are other alerts, you'll get those. > > > > [And I'm pretty sure it works that way. I don't have any currently > > configured child sections using this, but did one a while back and it > > functioned as specified here - at least IIRC it did. I was using > > 2.4.something - but I haven't heard of any different behavior in > > 2.6.x] > > Yesterday [email protected] wrote:
> Thank you, Greg > > Yes, I ended up defining all my parent alerts in one line in the Targets file: > > [...] Now that you understood. Do you want to suggest changes to Smokeping.pm (the documentation is in there ... just search for the strings ... ). cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
