• Notification within GreenLight
• Email alert over SMTP
• SMS alert (if equipment is available)
• SNMP Trap notification to another monitoring system
• Domino Console command issued to server (e.g. restart a task or the whole server)
• Sametime chat message
• Syslog message

 
An example alert within the GreenLight interface

A number of alerting configuration options allow you to avoid situations where you are flooded with eMails or needlessly alerted. Of course it is also possible to make notifications depending on wether an issue occurs during business hours or a maintenance period.

 

Alerting options within the notification and action interface

Example: if your pending mail count is at 1000 because somebody sent a mass mail, that might not be a problem as long as the Router works it off. However, if it's still that high after ten minutes, you will want to know about it. Every time that problem is detected? Probably not, three reminders should be enough. And if the issue is still unhandled after another 30 minutes a different notification can go out to a different group of people. Letting them know that GreenLight has automatically restarted the Router task ok the Dominio server.

Now this was just a fictional example of what can be achieved with our flexible alerting & action framework, but it should provide a good understanding of how the techniques can be used to make your life easier and introduce a basic self healing capability in your infrastructure.