Hobbit monitoring - no color change before bbretest?

I am currently monitoring a large network with Hobbit and have been tasked with reducing the number of false (or at least irrelevant) alarms. At the top of my list are the "http" and "conn" tests initiated by bbtest-net. This command checks ping, ssh, etc., and if for example ping time, it immediately sets the status to red. After one minute, the bbretest command runs, checks for any newly reddened hosts, and finds it green again. It happens all the time and it clogs my log.

Is there a way for me to make the Hobbit post a red status AFTER bbretest was run the first time?

+1


source to share


3 answers


I think your best bet is to avoid Hobbit maintenance mock tests and write your own. This is not difficult.

The good thing is that your test script won't be red if several consecutive attempts fail.



You can turn off the standard hobbits and use your own instead. Having said that, the default behavior of the "conn" test seems pretty reasonable (red right away if the server is not pinging).

Unfortunately, there is no way in the Hobbit alert system to warn if the problem persists within X minutes, that would be very helpful, but I'm sure you can do this too with a custom alert script.

0


source


Firstly, this is a programming site, so you won't get many answers.

But ... but ...

If your server is down isn't it a problem?



It seems to me that the Hobbit is on a mission meant to: Telling you that you have something that you need.

Fix the timeout problem and your log should be fine.

+2


source


You can use:

<ip> <hostname> # noconn 

      

In bb-hosts for a server that doesn't respond to ping. Then check your activity through the service.

0


source







All Articles