How about this contrived example:
page FOO A Page of FOOs
group Production Servers
0.0.0.0 .default. # DESCR:"Database Server:Juneau" 0.0.0.0 one.bar.com # sql
0.0.0.0 two.bar.com # ssh
group Test Servers
0.0.0.0 .default. # DESCR:"Database Server:Anchorage" nopropred:*
0.0.0.0 three.bar.com # sql https://three.bar.com/
0.0.0.0 four.bar.com # nopropyellow:+msgs
group Development Servers
0.0.0.0 .default # DESCR:"Development Hosts:No Callout" nonongreen nosslcert
0.0.0.0 five.bar.com # sql https://five.bar.com/
0.0.0.0 six.bar.com #
Each display group has its own default line. The line affects all hosts until the next .default. is encountered, which is why I put one at every display group. In my example above, each host in the group will get its 'DESCR" tag from the .default. line. Those in 'Test Servers' will also get nopropred for all tests, while four.bar.com will also get the msgs test added the nopropyellow list. Host five.bar.com will have an HTTPS test performed, but its .default. line will suppress the displaying of the certificate information from that test.
Hosts in the display group may be able to override the .default., but it depends on the tag. For example, the 'nopropred:*' could be overridden by a 'nopropred:msgs' on four.bar.com. I am, however, unaware of any negating command for 'nonongreen'; what would it be 'nononongreen' ? :)
It is very important to read the notes in the man page regarding which tags are available for use in .default.
NOTE: The ".default." host entry will only accept the following tags - others are silently ignored: delayyellow, delayred, NOCOLUMNS, COMMENT, DESCR, CLASS, dialup, testip, nonongreen, nodisp, noinfo, notrends, noclient, TRENDS, NOPROPRED, NOPROPYELLOW, NOPROPPURPLE, NOPROPACK, REPORTTIME, WARNPCT, NET, noclear, nosslcert, ssldays, DOWNTIME, depends, noping, noconn, trace, notrace, HIDEHTTP, browser, pulldata. Specifically, note that network tests, "badTEST" settings, and alternate pageset relations cannot be listed on the ".default." host.
Please note: "others are silently ignored"
--
Do things because y
ou should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
On 3/19/2018 5:07 AM, Scot Kreienkamp wrote:Can you supply an example? I didn't realize that could be used anywhere except globally.
Scot Kreienkamp |Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive| Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | | Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid
-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of John Thurston
Sent: Friday, March 16, 2018 2:17 PM
To: xymon at xymon.com
Subject: Re: [Xymon] nopropred
On 3/16/2018 9:34 AM, Jason Brockdorf wrote:
Is it possible for me to apply nopropred/nopropyellow/noproppurple tags to
groups and/or pages instead of hosts?
Only by use of the .default. line. I use such lines generously.
Each of my display groups has a .default. line. This lets me quickly set
attributes for hosts belonging to same support teams. And because each
group has a .default. line, I am never surprised by default lettings
leaking down from other display groups.
Such lines could just as easily be defined at the page-level, if that is
a better fit with your business requirements.
The .default. line was a major improvement when moving from Big Brother
to Xymon.