3 ms·
Can Cabot handle "multihomed" services? I have services running remotely, that are accessible through a variety of communication methods (VPNs, SSH tunnels, 3G
by beagle3 13y ago
Can Cabot handle "multihomed" services?
I have services running remotely, that are accessible through a variety of communication methods (VPNs, SSH tunnels, 3G modems, and occasionally just straight up IP!) and it's been awhile, but when I set up nagios, it seemed there was no way to tell it: "Alert if this host is not reachable in any of these 50 ways" - it monitors all 50, and alerts me whenever each one of them changes state (which is quite often).
What I want to say is: Here are all the ways I can reach server "pinky", I want a warning if there are less than 3 ways for more than an hour, and an alert if non of the way works for more than 3 minutes.
Can cabot do that?
(for that matter, can any other monitor do that?)
- sehrope 13y agoI'm not sure about Cabot (first time seeing it is today) but I've been designing a system that supports this type of monitoring. Shoot me an email (contact in profile) if you'd like to be contacted once it's up.
- mhurron 13y agoI think Zabbix can do what you want with trigger dependencies. https://www.zabbix.com/documentation/1.8/manual/config/host_and_trigger_dependencies https://www.zabbix.com/documentation/1.8/manual/config/host_... Though I'm not sure about the "warning if there are less than 3 ways for more than an hour" requirement.
- dbuxton 13y agoThis sort of service-oriented monitoring is very close to the pain point that caused us to create Cabot. In our case, it was more that there were multiple things we could monitor for that potentially indicated a problem with a service but it was hard, using Nagios or whatever, to tie those individual indicators back to a single service going haywire at 3am, especially if all 50 of them blow up at once. We don't have the precise problem that you describe though - for us the ability to monitor the number of data series in a graphite collection (so that if a server disappears we can notify, and then if another drops off we can alert) is sufficient. Cabot can use this and the ability to tolerate a number of failures to give behaviour very close to what you talk about. However I don't know if Cabot would support the kinds of checks that you're carrying out out-of-the-box, you'd probably have to extend.