> Notifications > Create a notification

Create a notification

Create a notification to alert your administrators or users of an issue occurring on the network. Notifications provide a means of staying on top of issues so that they can be resolved quickly with the minimum amount of downtime.

A notification is made up of a notification profile and one or more triggers. A notification profile is where you set up who is to be notified when a status changes, and if the alert escalates. That is, if it is not rectified after a certain time. Depending on the size and structure of your organization, you can have one notification profile and use it for all the notifications you create, or customize profiles for different combinations of monitored services and devices.

For notifications at the Service Organization level that apply to all customers, notification triggers are associated to rules. At individual customer level they can also be associated to specific devices and probes.

A notification cannot be added until a notification method has been set up for an account. To set up a notification method, click AdministrationUser Management > Users. Edit a user account and click User DetailsNotification Method.

After saving the profile, you cannot change the profile type. You will need to recreate the profile if you need to alter this setting.

  1. Click ConfigurationMonitoring > Notifications and click Add Notifications.
  2. Enter a name for the profile.
  3. Select the notification type.
    • Single Device, Single Service Notifications: This is the recommended notification type. A notification is generated for each service on each device, regardless of any notifications currently active. Use this option unless you need to suppress multiple tickets on a device.
    • Single Device, Multiple Service Notifications: .This triggers an alert for the first of the services covered in the notification and suppress alerts for any other services that are included in the same notification. This type is useful for application monitoring.
    • An example for using this type is Exchange. You might monitor four Exchange services, and only want to be alerted if one of them are down. You do not want to be alerted if the three other failed 20 minutes later.

    • Multiple Device, Single Service Notifications: This produces a single notification for each service, regardless of how many devices running this service fail. This means that if a service fails, no further alerts will be created for this service on any other device until the problem is resolved. This should be used with care, and is not recommended.
  4. Set a delay for the Primary Notification between when the status changes and when MSP N-central sends the alert.
  5. The delay ensures that the status change is not a temporary fluctuation a component's operation, such as CPU usage, and only want to be notified if the change continues for longer than a specified period.

  6. Select the recipients and time interval for an escalation of a notification. Notifications repeat until the issue is acknowledged or the status returns to Normal.
  7. Click Save and Continue.
  8. On the Trigger Details tab, click Add and enter a name for the trigger.
  9. Configure the details on what conditions and services trigger the notification. You can create as many triggers for a profile as required.
  10. Click OK, then Cancel.

You are returned to the Notifications page with the new notification appearing in the list. Notifications are sent when the trigger on the service has been activated.

Edit the profile by clicking on the notification name. You can edit a notification profile. When editing a Service Organization-level notification, the changes propagate to any Customer-level notifications that are based on the Service Organization-level notification.