Notifications

Notifications from your network

We have taken the notification logic a step further from the normal E-mail and SMS notifications and extended with notification skins and some new ways of notifying personal. Since a notification is just a call to some script, a notification can basically do anything, such as advanced escalations chains, turn on a red light and call the police.

Out-of-the-box notifications functionality

  • E-mail and SMS notifications
  • Skins and templates for e-mail and SMS notifications that can be customized per contact
  • Possible to notify via SNMP-trap
    • Easy integrate towards another monitoring system or ticket handling system
  • Possible to notify by dialing a contact until the call is answered
  • Advanced escalations-chains

Restrictive notification logic

Notifications are only sent if a number of requirements are met:

  • Your contact is configured to receive that type of notification
  • Your contact is configured to receive notifications within the current timeperiod
  • The host/service is not in a flapping state (back-and-forth between an OK state and a non-OK state)
  • The host/service is not in scheduled downtime

 

Tuning thresholds to minimize the amount of notifications

Any monitoring system, including op5 Monitor, needs to be adjusted to suit your organizations specific needs. To get rid of of false/uninteresting or exaggerated alerts (alarms/notifications) it is necessary to identify the source(s) of your notifications and adjusting thresholds and configuration. A new installation definitely needs tuning, but it’s also a good idea to generate reports on a regular basis to prevent being flooded with notifications.

 

Basic workflow

When tuning an op5 Monitor configuration you follow three basic steps:

  • Create a report to identify your top alert producers
  • Make decision based on fact on what to do
  • Perform a configuration change or acknowledge the problem (use comments).

 

If the problem needs to be fixed then acknowledge the problem and/or disable notifications and/or active checks of the host/service. If it’s a false, uninteresting or exaggerated source of alerts, then you must identify what needs to be adjusted and set new thresholds, time periods, timeouts and check_attempts.

Try op5 Monitor Enterprise+

Download full 30 day trial version, including all features, API and op5 App support

Download op5 Monitor

Alert Summary

op5 Monitor has out of the box reports generating lists of top alert producers, resulting in problem-state notifications, i.e, the alerts you get SMS and/or e-mail about.

 

Notifications: Example of a report showing top alert producers

Example of a report showing top alert producers

Notifications_list

Notifications list

Finding the problem

Using the Alert Summary Report as a starting point, you can click on the host/service-names in the report to reach the host/service-information-pages. In the information-pages you can:

  • Take a look at a simple graphs (for the most common services)
  • See how long you’ve had the problem (Current State Duration)
  • Read any comments about the host/service
  • Reach even more detailed views about the problem