How you act in the event of a network fault depends on the criticality of the failure. Not all faults require immediate attention but at the same time, there can also be 'high priority' alerts that need instant attention while others need further drilling-down and analysis. OpManager makes it easier for you to attend to your network faults by employing different alerting mechanisms. All you need to do is set up which type of alerting you'd want given the severity or priority of the alert. Lets get to some more details on the possible network fault alerting capabilities in OpManager.
Emailing alerts: Configure an Email notification profile in OpManager to trigger automatic emails to an email ID or to a group. The network engineer responsible for the specific alert will be notified instantly. For instance, an email alert can be triggered to the virtualization admin team if there is any critical VMware or HyperV alert needing special and instantattention. Depending on the access provisions, the concerned admin can immediately attend to the problem.
SMS alerts: You can also configure OpManager to text an alert to a specific mobile number, so the concerned person gets to attend to the failure without any delay. The SMS alerts could either be email-based or modem-based. The administrator can readily access and drill-down the alert from anywhere if he has a smartphone.
Escalating alerts: This is the next level of notification mechanism where you can configure OpManager to let the next level of IT administrators or managers know about a fault not attended to in a while. It also serves as a reminder to let a person or team know that a fault is pending for longer than it should. For instance, IT managers can setup an escalation rule to get a report of server alarms that are currently open for more than one hour. The escalation can happen over an email to the IT Manager's email Id or as an SMS notification.
Raising trouble-tickets in SDP: Log trouble tickets automatically in ServiceDesk Plus for specific network monitoring alerts and automatically assign them to the appropriate team or technician. This option is mostly useful if the alert can wait, and if it needs tracking over a period. For instance, a shift administrator may want to work on a particular alert. All he'll need to do is, log into his ticketing portal and pick the tickets assigned to him. SDP also has a mechanism to notify a techinician when tickets are assigned. The alerts are automatically cleared when a ticket is closed.
Forwarding alerts to another manager: Some enterprises prefer to have a centralized console for tracking alerts. OpManager now has the capability of forwarding OpManager alerts, SNMP traps, and Syslog messages to other managers either as traps or syslog messages. It can forward the processed alerts or simply bounce off the incoming SNMP traps and Syslog messages to another receiver/manager.
Web Alerts: Different IT personnel might be logged into OpManager for different reasons. The web alerts draws your attention by generating a sound and also by indicating with a glow.
If you want to see additional network fault monitoring features implemented in OpManager, we would love to hear. Click here to continue