[Xymon] Preventing Purple - Periodical Checks

[Tracy Di Marco White]

We have a bunch of feeds that happen on odd schedules, and they go red or yellow on various problems, but are usually green. On days or times that there is no feed to process, the test goes clear. We usually set the lifetime to at least two iterations of the test, so there are no purples unless there is a different problem. 

-Tracy

> On Sep 23, 2014, at 8:48 AM, <john.r.rothlisberger at accenture.com> <john.r.rothlisberger at accenture.com> wrote:
> 
> What we do, and it has proven to be very helpful, at least for purple indications of Windows clients.
>  
> We send email alerts when “disk” has been purple for over 30 minutes.
>  
> Why, you may ask.  There are specific instances when tests go purple and there is no need to alert on all tests.  If disk is purple, most likely all the rest are purple except for connection.
> The number one cause of purple alerts is that the BBWin service is not running. Please check this service FIRST and start/restart if necessary.
> The client server is hung, sometimes it will respond to a ping and not otherwise indicate that it is down.
> The C drive is full.
> 99% of the time the purple is not indicative of a server issue, but when it is, sometimes this is the only way to catch it early.
>  
> Thanks,
> John
> Upcoming PTO:
> (none)
>  
> _____________________________________________________________________
> John Rothlisberger
> IT Strategy, Infrastructure & Security - Technology Growth Platform
> TGP for Business Process Outsourcing
> Accenture
> 312.693.3136 office
> _____________________________________________________________________
>  
> From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Tres Finocchiaro
> Sent: Monday, September 22, 2014 2:55 PM
> To: xymon at xymon.com
> Subject: [Xymon] Preventing Purple - Periodical Checks
>  
> I have a custom service check that is only done during certain times of the day and only on certain days of the week.
>  
> We use crontab and a shell script to generate the output and pipe it into the front-end using the xymon executable.
>  
> xymon 127.0.0.1 "status $server.$service $green|$red|$yellow $timestamp,$description"
>  
> This check works terrific when it runs, but in between checks it goes purple.
>  
> Without creating a fake service check in between each scheduled cron entry, what's the quickest way to configure that this check goes purple less often?  (or if that's not possible, never go purple?)  How are others handling occasional or daily service checks?  Are you hard-coding the times into the script itself?
>  
> -Tres
>  
>  
> 
> - Tres.Finocchiaro at gmail.com
> 
> 
> 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
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20140923/c37fc259/attachment.html>