Thought I would mention solution here in case it saves some other folks a lot of head scratching.

It turns out that the analysis.cfg file (and probably the alarm.cfg as well) seem to be whitespace-sensitive. That is to say, if your "LOAD" command doesn't begin at position 1 on the line, it may be interpreted as a combination condition with the line above. (of course, one may wish to combine several metrics for a single host, using the indented notation, but that is an intended whitespace)

From: Xymon <xymon-bounces at xymon.com> On Behalf Of Lynn Osburn Sent: Thursday, June 07, 2018 9:12 AM To: xymon at xymon.com Subject: [Xymon] EXTIME/TIME syntax

Attempting to prevent "false" cpu alarms during overnight processing, I have included a line in analysis.cfg thus: LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400

However, alarms continue to be generated during the "excluded" hours.

Has anyone else had any difficulty with either TIME or EXTIME entries?

Thanks!