Need syntax eyes on badtest entry
list Xymon User in Richmond
I'm trying to give a little resiliency to reporting on an Outlook Web Access server that intermittently returns bad https results without visibly disrupting user services. "badhttps" doesn't seem to be working for me. I have: xx.xxx.xx.xxx webmail.example.com # noconn noping https://webmail.vita.example.com/Exchweb/bin/auth/owalogon.asp badhttps:2:3:5 \ COMMENT:"external prod Shared E-mail Web Interface" IP and hostname are of course obfuscated. It's on two lines, as indicated by the "\". But it still appears to go red on a single https failure. Can anyone out there point out my error?
list Josh Luthman
Never done badhttps but are you sure \ works in bb-hosts?
▸
On 6/23/10, Xymon User in Richmond <user-24d6f8323faa@xymon.invalid> wrote:I'm trying to give a little resiliency to reporting on an Outlook Web Access server that intermittently returns bad https results without visibly disrupting user services. "badhttps" doesn't seem to be working for me. I have: xx.xxx.xx.xxx webmail.example.com # noconn noping https://webmail.vita.example.com/Exchweb/bin/auth/owalogon.asp badhttps:2:3:5 \ COMMENT:"external prod Shared E-mail Web Interface" IP and hostname are of course obfuscated. It's on two lines, as indicated by the "\". But it still appears to go red on a single https failure. Can anyone out there point out my error?
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
“Success is not final, failure is not fatal: it is the courage to
continue that counts.”
--- Winston Churchill
list Torsten Richter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am pretty sure that there is no such thing as badhttps only badhttp. Just try without the 's' and it should work. At least for my servers I have the badhttp even for https URLs and it is working as expected. HTH Torsten
▸
On 23.06.2010 16:55, Xymon User in Richmond wrote:I'm trying to give a little resiliency to reporting on an Outlook Web Access server that intermittently returns bad https results without visibly disrupting user services. "badhttps" doesn't seem to be working for me. I have: xx.xxx.xx.xxx webmail.example.com # noconn noping https://webmail.vita.example.com/Exchweb/bin/auth/owalogon.asp badhttps:2:3:5 \ COMMENT:"external prod Shared E-mail Web Interface" IP and hostname are of course obfuscated. It's on two lines, as indicated by the "\". But it still appears to go red on a single https failure. Can anyone out there point out my error?
- -- +---------------------------------------------------------+
| E-mail : user-c862b499d9fa@xymon.invalid | | | | Homepage: http://www.richter-it.net/ | +---------------------------------------------------------+ Download my public key from: http://gpg-keyserver.de/pks/lookup?search=0x899093AC&op=get -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iEYEARECAAYFAkwiNOYACgkQ7DlmxomQk6xx2QCeNOG78LisWAMR8xYd8WoKJMSd bl4An0E638iEILbHZB5h4HIzW2+FVdlS =Pmg9 -----END PGP SIGNATURE-----
list Epperson
On Wed, June 23, 2010 11:12, Josh Luthman wrote:
Never done badhttps but are you sure \ works in bb-hosts?
Yes. I've used it to set off COMMENT and NOCOLUMN lines for years.
list Xymon User in Richmond
▸
On Wed, June 23, 2010 11:12, Josh Luthman wrote:
Never done badhttps but are you sure \ works in bb-hosts?
Yes. I've used it to set off COMMENT and NOCOLUMN lines for years.
What DOESN'T work is "badhttps". It's "badhttp", even for https. Just
got it working.