Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We send notifications to our clients when we are scheduling system maintenance, or if the system is down or running slow. We use several methods of communication (email, web site status message, twitter, blog entries, phones). The problem with this approach is that these services are either hosted by us, our requires our internet connection to be useful.

We had a significant failure last week. I don't have all the details but in a nut shell a T1 went down and the fail-over failed. Email, phones, internet, ftp were down.

I'm a programmer and I suggested that I build a utility that automates most of these notification tasks from a simple web interface. This does no good if we host it internally and we are down. We need to move the notification services off-site somewhere.

My fear in doing this is that if the system notifications start coming from another domain, people are going to be scratching their heads; some may even disregard the alerts.

Any suggestions?

share

locked by HopelessN00b Apr 3 at 13:15

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as too broad by HopelessN00b Apr 3 at 13:14

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer 1

Can you perhaps host your notification software on another host at another location/on another Internet connection, but have it resolve to a subdomain of your current domain? For example, if you're currently monitoring at example.com, you could move your service to monitor.example.com and start sending notifications from there.

As for the utility, you might look into Nagios - it's a reasonably complete suite of monitoring tools that can watch web services, FTP, email, the works. You can host it separately and just configure all your main services to send status to the Nagios host, then configure Nagios to send alerts if it doesn't hear from the main site for a certain period of time or if the main site starts acting unexpectedly.

share
    
The process has become bureaucratic. I wonder if Nagios has a staging area for these messages where they get queued up but can't be sent until they are approved. I'll check it out. –  Billy Coover May 19 '09 at 5:41
    
We use NetIQ to monitor... Everything. In fact, we just hired a NetIQ guru to put it to good use. So, we are set with monitoring. It's the notification that we worry about. NetIQ is great when then network is up, but when it's down, the NetIQ notifications become useless. –  Billy Coover May 20 '09 at 22:17

Not the answer you're looking for? Browse other questions tagged or ask your own question.