Define notification policy for services

On the page

Need some help?

setting a notification policy for a service consists of defining...

  • ...for what events...
  • ...what time slot...
  • ...who to inform

The events triggering the notification policy on a service are changes to the status of that service.

The notification policy can be defined for a single service, or for a group of services.

Important :

The applied notification policy is arrived at by logically merging the notification settings defined at the contact level and those defined at the service level. This business rule allows you to have granular management of notifications.

Example: a notification time range from 0:00 to 24:00 is defined at the CPU service level. The notification time slot 5h-12h is defined for Team A, the notification time slot 12h-20h is defined for Team B.

  • If a change of status occurs at 13:00, the B-team will be informed.
  • If a change of status occurs at 10:00, the A-team will be informed.
  • If a change of status occurs between 8pm and 5am, no team will be notified, but if the problem is still present at 5am then team A will be notified.


Notification policy for a single service

Place your focus on the company at which you want to define the notification policy for a service.

  1. Navigate to Configuration > General > Services > List.
  2. Search for and then click on the service you wish to configure: the service details are displayed on the screen.
  3. Select the Notifications tab on this page.

ServiceNav - Configuration - List of unit services



ServiceNav - Unit Service - notification configuration


On this page, configure the notification policy as follows:

  1. Click Yes to enable notification on the host
  2. Select in the drop-down list the notification time range you want (default leave: 00h - 24h MTWTFSS)
  3. Select the host status changes that will cause the notification policy to be triggered
  4. Indicate if additional checks should be carried out before sending the first notification and confirming the status change of the host.
  5. If you select the event " Unstable" Specify the upper and lower thresholds that define the instability status of a host (do not select defaults).
  6. Select the contacts and contact groups that will be alerted by the notification sent. Only contact groups and active contacts are presented in the lists.


Notification policy for a group of services

It is possible to apply the same notification policy to a group of services by making multiple selections.

Place yourself in the company for which you want to define the notification policy for services.

  1. Navigate to Configuration > General > Services > List.
  2. Select services of the same criticality, those for which notification is enabled or disabled, services based on the same service template, services containing the same string. This step is optional.

ServiceNav - Configuration - Selection of all unit services

Tip: Choose to display all services on one page by selecting the number of items as " All " :

ServiceNav - Tip - display all unit services on one page


Click on the " More"button and then select " Change the notification policy " :

ServiceNav - Unit services - mass notification modification action


Then select " Yes "and configure the desired notification policy:

ServiceNav - Unit Service - mass notification configuration


This may also be of interest to you

IMG 0006

Set up notifications to Microsoft Teams

IMG 0006

Configure Exim emailing with Microsoft Office365

ServiceNav Configuration Contact group

Define a contact group


Welcome to ServiceNav!

Need help? More information about our products? Write to us!
You have taken note of our privacy policy.


While the epidemic lasts, ensure the availability and performance of your IT services for teleworking, with ServiceNav!

Following the government's call to mobilize to help businesses overcome the current health and economic context, we help you, free of charge, to ensure the complete monitoring of your teleworking environments: VPN, VDI, Teams, Skype Enterprise, Citrix... Objectives: collection, availability and usage indicators, dashboards to support your communication.
We use cookies to ensure that you have the best possible experience on our site, and if you continue to use this site, we will assume that you are satisfied with it.

Reserve your place

You have taken note of our privacy policy.