November 2017 - Xymon - Xymon mailman web

Capture and send data To Elasticsearch and Kibana
by francois.outteryck＠soprasteria.com 27 Sep '22

27 Sep '22

Hi Peter, Examples of task.cfg configuration with status and stachg events : [capture_status] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture.log LOGFILE /var/log/xymon/lunch_capture.log [capture_stachg] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=stachg /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture_stachg.log LOGFILE /var/log/xymon/lunch_capture_stachg.log Capture.sh script simple made to call a php script : #!/bin/sh /usr/bin/php /var/www/kibana/capture.php $@ </dev/stdin >>/var/log/xymon/xymond_capture_php.log 2>&1 And capture.php make all job : <?php date_default_timezone_set('Europe/Paris'); $TODO=FALSE; $ARRAY_COLLECTOR=array(); $COLLECTOR=null; while (FALSE !== ($line = fgets(STDIN))) if ($line!='') { $tab=reduce_array($line); if (sizeof($tab)==0) continue; if ($line=="@@\n") { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } else if (substr($tab[0],0,8)=='@@stachg') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@stachg#seq|timestamp|sender|origin|hostname|testname|expiretime|color|prevcolor|changetime|disabletime|disablemsg|downtimeactive|clienttstamp|modifiers */ $COLLECTOR='stachg'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'PrevStatus'=>$metadata[8], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[9], 'DisableTime'=>$metadata[10], 'DisableMSg'=>$metadata[11], 'Message'=>'' ); $id=$metadata['ServerName'].'_'.$metadata['Type'].'_'.$meta['LastChange']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else if (substr($tab[0],0,8)=='@@status') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@status|timestamp|sender|origin|hostname|testname|expiretime|color|testflags|prevcolor|changetime|ackexpiretime|ackmessage|disableexpiretime|disablemessage|clientmsgtstamp|flapping */ $COLLECTOR='status'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[10], 'DisableTime'=>$metadata[13], 'AckTime'=>$metadata[11], 'DisableMSg'=>$metadata[14], 'Message'=>'' ); $id=$metadata['ServerName'].'.'.$metadata['Type']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else { if (substr($tab[0],0,2)=='@@') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } if ($TODO) $ARRAY_COLLECTOR[]=$line; } } function CallAPI($method, $url, $data = false) { $curl = curl_init(); switch ($method) { case "POST": curl_setopt($curl, CURLOPT_POST, 1); if ($data) curl_setopt($curl, CURLOPT_POSTFIELDS, $data); break; case "PUT": curl_setopt($curl, CURLOPT_PUT, 1); break; default: if ($data) $url = sprintf("%s?%s", $url, http_build_query($data)); } curl_setopt($curl, CURLOPT_URL, $url); curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1); $result = curl_exec($curl); curl_close($curl); return $result; } function reduce_array($line) { $tab=explode(' ',$line); $nr=array(); for ($i=0;$i<sizeof($tab);$i++) if (trim($tab[$i])!='') $nr[]=trim($tab[$i]); return $nr; } function SendData($id,$cc,$COLLECTOR=null) { if ($COLLECTOR==null) return; $d=new DateTime(); if ($cc['LastChange']!='') {$d->setTimestamp($cc['LastChange']);$cc['LastChange']=$d->format('c');} else {$cc['LastChange']='NaN';} if ($cc['LogTime']!='') {$d->setTimestamp($cc['LogTime']);$cc['LogTime']=$d->format('c');} else {$cc['LogTime']='NaN';} if ($cc['ValidTime']!='') {$d->setTimestamp($cc['ValidTime']);$cc['ValidTime']=$d->format('c');} else {$cc['ValidTime']='NaN';} if (isset($cc['AckTime'])) { if ($cc['AckTime']!='') {$d->setTimestamp($cc['AckTime']);$cc['AckTime']=$d->format('c');} else {$cc['AckTime']='NaN';} } if ($cc['DisableTime']!='') {$d->setTimestamp($cc['DisableTime']);$cc['DisableTime']=$d->format('c'); } else {$cc['DisableTime']='NaN';} $data = json_encode($cc); $data=str_replace('"NaN"','null',$data); echo $id.'=>'.$data."\n"; $url="http://127.0.0.1:9200/xymon/".$COLLECTOR."/".$id; $res=CallAPI("POST",$url,$data); } ?> De : Peter Welter [mailto:peter.welter at gmail.com] Envoyé : vendredi 23 décembre 2016 14:45 À : OUTTERYCK Francois Cc : xymon at xymon.com Objet : Re: [Xymon] Capture and send data To Elasticsearch and Kibana Hi Francois, Looks good, your sample. I am very interested in your integration efforts. How do you select what is going to be inserted in the ELK stack? All status messages that Xymon receives? And could you provide an example of the xymond_channel block in you task.cfg and the capture.sh? Tasks.cfg probably is something like: [es] ... CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh ... And the capture.sh contains some curl script to the ELK stack? Regards, Peter 2016-12-14 18:15 GMT+01:00 OUTTERYCK Francois <francois.outteryck at soprasteria.com<mailto:francois.outteryck at soprasteria.com>>: Hello, I just do a small work with Xymon in order to send status data to Elasticsearch. And with Kibana reporting is easy. How it work ? Simple : With capture of status message (xymond_channel --channel=status /home/xymon/server/ext/capture.sh ) script encode status message in json and send as document in elasticSearch. Example of Mapping document status in elasticsearch : "status"=> array( "properties"=>array( "ServerName"=> array("type"=> "string"), "Type"=> array("type"=> "string"), "Status"=> array("type"=> "string"), "LastChange"=> array("type"=> "date","format"=> "strict_date_optional_time"), "LogTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "ValidTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "AckTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "DisableTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "Sender"=> array("type"=> "string"), "DisableMSg"=> array("type"=> "string"), "Message"=> array("type"=> "string") ) ) All is done with a 130 lines script. So simple to integrate in existing environment and so powerfull usage of Xymon/elasticsearch/Kibana For those who don’t know kibana : https://www.elastic.co/products/kibana [cid:image001.png at 01D25EA3.F74489F0] _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

2 1

Need help with upgrade from 4.3.17 to 4.3.20
by cleaver＠terabithia.org 17 Jul '18

17 Jul '18

Hmm. So far, the only way I've been able to reproduce this is by replacing the ScriptAlias directives with mere Alias's in the xymon.conf apache config. Has there been any change in the path you've used for the CGI directory since the previous version, or is there any chance that another Alias line is taking precedence over the ScriptAlias? Do you see anything in the apache access/error logs that indicates an error? -jc On Tue, May 19, 2015 10:37 am, Cortes, Manny wrote: > Having the same problem after installing 4.3.20 on both Ubuntu server > 14.04 and 15.04. > > Thanks, > > > Manuel A Cortes > > Systems Programmer III > > [IBM_Cert] > > IBM Certified System Administrator AIX 7 > > Information Services > > 321-841-6534 > > Orlandohealth.com > > Facebook.com/orlandohealth > > Youtube.com/orlandohealth > > @orlandohealth on twitter > > > > 1414 Kuhl Avenue.,MP136 > > Orlando, Florida 32806 > > From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Asif Iqbal > Sent: Tuesday, May 19, 2015 12:59 PM > To: J.C. Cleaver > Cc: xymon at xymon.com > Subject: Re: [Xymon] Need help with upgrade from 4.3.17 to 4.3.20 > > > > On Tue, May 19, 2015 at 12:40 PM, J.C. Cleaver > <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> wrote: > Hmm. It seems like it's trying to pass along the binary rather than > actually execute it. Can you > > a) validate the permissions on the various .sh files inside the > /xymon-cgi/ directory. (Wondering if there's a case where make install > doesn't set permissions properly), and > > > /var/lib/xymon/cgi-bin$ ls -al > total 6560 > drwxr-xr-x 2 root root 4096 May 19 10:19 . > drwxr-xr-x 16 xymon xymon 4096 May 19 10:19 .. > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 acknowledgements.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 certreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 columndoc.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 criticalview.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 csvinfo.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 datepage.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 eventlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 findhost.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 ghostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 historylog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 history.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostgraphs.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 nongreen.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 notifications.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 perfdata.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 reportlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 report.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 showgraph.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 snapshot.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 svcstatus.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 topchanges.sh > > > b) verify that the ScriptAlias or ExecCGI options are still present in > apache.conf. > > > grep xymon-cgi /etc/apache2/sites-enabled/xymon-apache.conf > # "/xymon" and "/xymon-cgi" URLs. > ScriptAlias /xymon-cgi/ "/var/lib/xymon/cgi-bin/" > RewriteRule ^/xymon-cgi/bb-hist.sh /xymon-cgi/history.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-eventlog.sh /xymon-cgi/eventlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-rep.sh /xymon-cgi/report.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-replog.sh /xymon-cgi/reportlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-snapshot.sh /xymon-cgi/snapshot.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-findhost.sh /xymon-cgi/findhost.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-csvinfo.sh /xymon-cgi/csvinfo.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitcolumn.sh /xymon-cgi/columndoc.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-datepage.sh /xymon-cgi/datepage.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitgraph.sh /xymon-cgi/showgraph.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-hostsvc.sh /xymon-cgi/svcstatus.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-histlog.sh /xymon-cgi/historylog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport.sh /xymon-cgi/confreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport-critical.sh > /xymon-cgi/confreport-critical.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nkview.sh /xymon-cgi/criticalview.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-certreport.sh /xymon-cgi/certreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nongreen.sh /xymon-cgi/nongreen.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostgraphs.sh /xymon-cgi/hostgraphs.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-ghosts.sh /xymon-cgi/ghostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-notifylog.sh /xymon-cgi/notifications.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostlist.sh /xymon-cgi/hostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-perfdata.sh /xymon-cgi/perfdata.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-topchanges.sh /xymon-cgi/topchanges.sh > [R=permanent,L] > > > HTH, > > -jc > > > On Tue, May 19, 2015 7:56 am, Asif Iqbal wrote: >> I am not sure what I need to after the upgrade for the columns to show >> data >> instead of >> something like this >> >> >> ELF ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½>ï¿½ ï¿½ï¿½ï¿½ >> @ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ Ã >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½8ï¿½ ï¿½@ï¿½%ï¿½"ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½8 ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½8 >> @ï¿½ï¿½ï¿½ï¿½ï¿½8 @ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> >> I removed FollowSymLinks from xymon-apache.conf file under /xymon-cgi/ >> and /xymon-seccgi/ and restarted. >> >> I am using ubuntu >> >> -- >> Asif Iqbal >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com<mailto:Xymon at xymon.com> >> http://lists.xymon.com/mailman/listinfo/xymon >> > > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > ________________________________ > > This e-mail message and any attached files are confidential and are > intended solely for the use of the addressee(s) named above. If you are > not the intended recipient, any review, use, or distribution of this > e-mail message and any attached files is strictly prohibited. > > This communication may contain material protected by Federal privacy > regulations, attorney-client work product, or other privileges. If you > have received this confidential communication in error, please notify the > sender immediately by reply e-mail message and permanently delete the > original message. To reply to our email administrator directly, send an > email to: postmaster at orlandohealth.com . > > If this e-mail message concerns a contract matter, be advised that no > employee or agent is authorized to conclude any binding agreement on > behalf of Orlando Health by e-mail without express written confirmation by > an officer of the corporation. Any views or opinions presented in this > e-mail are solely those of the author and do not necessarily represent > those of Orlando Health. >

8 25

Problems with Content Security Policy in Safari, Chrome, and IE
by jtrott＠dancrai.com 22 Mar '18

22 Mar '18

Xymon 4.3.28-1.el7.terabithia with Safari 11 on High Sierra and Safari on iOS 11. Problem occurs on the trends page. https://xymon.domain.com.au/xymon-cgi/svcstatus.sh?HOST=host.com.au&SERVICE… If you click on any of the time based buttons, 48hrs for example, the requested page doesn't load. Safari on macOS look like it's loading a page but doesn't get anywhere. Safari on iOS does nothing at all when you tap the button. The console in Safari reveals the following error: Refused to load https://xymon.domain.com.au/xymon-cgi/svcstatus.sh?HOST=host.com.au&SERVICE… because it does not appear in the form-action directive of the Content Security Policy. Checking the headers shows this content security policy: Content-Security-Policy: script-src 'self' 'unsafe-inline'; connect-src 'self'; form-action 'self'; sandbox allow-forms allow-scripts; I'm not that well versed in the CSP stuff, but I note that it also fails with the same error in the latest Chrome 62.0.3202.89, and in Internet Explorer 11.0.9600.18817 (no error logged), but works in the latest Firefox 56.0.2. Has anyone else run into this issue, or has any more information on how I can modify the CSP headers to test? I tried using Header set Content-Security-Policy in apache but that seems to add an improperly formatted addition to the rules rather than overwriting them. Thanks, JT

5 9

Recovery notifications not generated when test goes red->yellow->green?
by hobbit＠elyograg.org 13 Dec '17

13 Dec '17

It appears that if a test goes from the red state, to the yellow state, and then to the green state, no recovery notification is sent. If it goes directly from red to green, then we get a notification. Initial notifications are only sent on RED and PURPLE. We have recovery notifications configured for most tests. Xymon server is 4.3.21, built using makerpm.sh and installed with yum on CentOS 6. I do not know whether our previous version (4.3.14) behaved similarly. It was almost an accident that I discovered the problem at all. Is this expected behavior? If it is, can I change it? Thanks, Shawn

4 3

Combo Combo Status
by lukas.kohl＠ergodirekt.de 29 Nov '17

29 Nov '17

Hey Guys, I have a Combo Status, which combines other combo states. The states are working technically fine, so that a red state in a subcombo is treated as 0 and is affecting the top state. So it works good for most cases. The problem I have is, that the States, which are consisting of combos are shown as &unknown (instead of &red or &green) in the xymon page (where a single combo test is working fine). I will attach a Screenshot for clarification. You can reproduce the error by simply building a combo out of a combo state. Combo from Combo (no gifs): Subcombo (working fine with gif): Best regards, Lukas _______________________ ERGO Direkt Lebensversicherung AG · Amtsgericht Fürth HRB 2787 · UST-ID-Nr. DE159593454 ERGO Direkt Versicherung AG · Amtsgericht Fürth HRB 2934 · UST-ID-Nr. DE159593438 ERGO Direkt Krankenversicherung AG · Amtsgericht Fürth HRB 4694 · UST-ID-Nr. DE159593446 Vorsitzender des Aufsichtsrats der ERGO Direkt Lebensversicherung AG: Dr. Dr. Michael Fauser Vorsitzende des Aufsichtsrats der ERGO Direkt Versicherung AG: Dr. Monika Sebold-Bender Vorsitzender des Aufsichtsrats der ERGO Direkt Krankenversicherung AG: Dr. Clemens Muth Vorstände: Peter Stockhorst (Vorsitzender), Dr. Jörg Stoffels, Ursula Clara Deschka · Sitz: Fürth Karl-Martell-Straße 60 · 90344 Nürnberg · Internet: ergodirekt.de UniCredit Bank AG - HypoVereinsbank Kto.-Nr.: 66 071 430 · BLZ 700 202 70 IBAN: DE63 7002 0270 0066 0714 30 · BIC: HYVEDEMM

2 1

NFR: "All Red View"
by robert.herron＠gmail.com 27 Nov '17

27 Nov '17

Cool. Learn something new everyday. The red.html is generated using the web/stdnongreen_header -- at least for 4.3.17. The page title is "Current non-green Systems" which is misleading. I add a web/stdred_header and updated it as appropriate. How much trouble is it to make Xymon use a different header template for generating the red.html ? On Nov 26, 2017 6:13 PM, "Jonathan Trott" <jtrott at dancrai.com> wrote: I'm pretty sure that one is already there. https://xymonserveraddress/red.html You just need to modify the xyonmenu.cfg file to add it into the menu. Thanks, JT From: Alessandro Tinivelli <Alessandro.Tinivelli at faacgroup.com> To: "xymon at xymon.com" <xymon at xymon.com> Date: 27/11/17 09:35 Subject: [Xymon] NFR: "All Red View" Sent by: "Xymon" <xymon-bounces at xymon.com> ------------------------------ Hi all, the longer I’m working with Xymon, the better i find it. And it’s more than 10 years, I guess J I would love to find another view, in the style of the “all non green view”: the “all red view”. It’d be really useful, in my opinion. Just my 2 cents ;) Best regards *Alessandro Tinivelli* _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1 0

Alert transition yellow -> red with repeat problem
by john.r.rothlisberger＠accenture.com 27 Nov '17

27 Nov '17

This problem contributed to an outage last night - something is wrong. Last night we had a disk that was in the warning state - warning email sent. That disk then went into an alert state and an alert email was triggered (right away as the DURATION value took into account the time it was yellow) and then again 15 minutes later as designed. THEN - another disk on that server went yellow. It did NOT trigger any emails (as expected we should continue to focus on the alerts) but it somehow interfered with the REPEAT time of the alerts and those STOPPED. There is a bug somewhere. Thanks, John Upcoming PTO: _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ From: Rothlisberger, John R. Sent: Tuesday, April 11, 2017 7:49 AM To: 'xymon >> xymon at xymon.com' <xymon at xymon.com> Subject: Alert transition yellow -> red with repeat problem This is a problem I have seen for a long long time and have actually brought it up on the list before. Xymon 4.3.21 Ubuntu 14.04LTS The problem I have (in this instance) a warning which is to be repeated daily suddenly goes red and triggers a single alert but doesn't repeat again until the repeat time of the warning has passed. >From the notification.log: Tue Mar 28 05:31:28 2017 ServerA.disk (IP) disk_warn 1490697082 100 <- warning sets a repeat time of 1 day Tue Mar 28 05:53:32 2017 ServerA.disk (IP) disk_alert 1490698405 100 <- minutes later it goes red (red repeat time is 15 minutes but no further alerts are generated) Next alert comes out 1 day after the above warning: Wed Mar 29 05:31:31 2017 ServerA.disk (IP) disk_alert 1490783486 100 <- 1 day after previous warning. This should have been repeated every 15 minutes. Wed Mar 29 05:46:40 2017 ServerA.disk (IP) disk_alert 1490784394 100 <- now, the repeat time is 15 minutes ... <- and continues every 15 minutes. This alert went a full 24 hours with only a single notification. :( I have seen this before (not always) where the repeat time in a warning overrides a follow up alert until the warning repeat time has expired. Alert rules: SCRIPT /home/xymon/server/ext/pg/exwarn_SCRIPT disk_warn DURATION>30 REPEAT=1d COLOR=yellow SERVICE=disk FORMAT=TEXT UNMATCHED SCRIPT /home/xymon/server/ext/pg/exalert_SCRIPT disk_alert DURATION>20 REPEAT=15 COLOR=red SERVICE=disk FORMAT=TEXT UNMATCHED Ideas/thoughts? Thanks, John Upcoming PTO: 4/3 _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com

3 5

NFR: "All Red View"
by Alessandro.Tinivelli＠faacgroup.com 26 Nov '17

26 Nov '17

Hi all, the longer I'm working with Xymon, the better i find it. And it's more than 10 years, I guess :) I would love to find another view, in the style of the "all non green view": the "all red view". It'd be really useful, in my opinion. Just my 2 cents ;) Best regards Alessandro Tinivelli

2 1

Xymon to monitor HP OpenVMS
by Jose.LeusJr＠analog.com 26 Nov '17

26 Nov '17

Resending, seems your mail is only accepting 100kb below. From: Leus Jr, Jose Sent: Sunday, November 26, 2017 10:09 AM To: Jeremy Laidman <jlaidman at rebel-it.com.au> Cc: David Boyer <davieb at gmail.com>; xymon at xymon.com Subject: RE: [Xymon] Xymon to monitor HP OpenVMS Thanks a lot Jeremy for helping me out on this. Here’s the snapshot of the cpu graph. [cid:image004.jpg at 01D3669E.D73A3B60] I’m looking forward for the integration of other OPENVMS resources to Xymon. At this time, below are the only resources I was able to monitor. [cid:image005.jpg at 01D3669E.D73A3B60] Sincerely, Leus From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Sunday, November 26, 2017 10:02 AM To: Leus Jr, Jose <Jose.LeusJr at analog.com<mailto:Jose.LeusJr at analog.com>> Cc: David Boyer <davieb at gmail.com<mailto:davieb at gmail.com>>; xymon at xymon.com<mailto:xymon at xymon.com> Subject: Re: [Xymon] Xymon to monitor HP OpenVMS Just to close this case, in case it helps others using OpenVMS, it turns out the client was an old BB client, which sent its CPU status message with "Up since <date>" rather than "up: <days> days". The difference is that the Xymon CPU status message parsing code expects "up: " (lower-case "up", colon, space). The script that generates the status message was adjusted, and the RRD file came into existence. In summary, there were some stale rrdctl files being used by Xymon, causing the original error message in the Apache logs. But the client was also not 100% compatible with Xymon. Both now fixed. J

1 0

Xymon to monitor HP OpenVMS
by Jose.LeusJr＠analog.com 26 Nov '17

26 Nov '17

Resending, From: Leus Jr, Jose Sent: Monday, November 20, 2017 7:49 PM To: Jeremy Laidman <jlaidman at rebel-it.com.au>; David Boyer <davieb at gmail.com> Cc: xymon at xymon.com Subject: RE: [Xymon] Xymon to monitor HP OpenVMS Hi Jeremy, David, Below is the captured logs from tail -f error_log-20170930 during selection of any graphs. This is also appeared in other hosts being monitored except that, other hosts(linux,windows) cpu graphs are ok. [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.250081 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.253708 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.255815 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.256007 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.265461 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.268706 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.271303 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] 2017-11-20 19:36:25.271476 , referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:36:25 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/showgraph.sh?host=promph1.analog.com&servic… [Mon Nov 20 19:37:29 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:29.901849 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:29 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:29 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:29.902058 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:29 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.076192 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.076388 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.083368 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.083768 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.089486 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] 2017-11-20 19:37:53.089697 , referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… [Mon Nov 20 19:37:53 2017] [error] [client 10.116.131.209] Sendto failed: Connection refused, referer: http://adgtbigbrother/xymon-cgi/svcstatus.sh?HOST=promph1.analog.com&SERVIC… Sincerely, Leus

2 11