Welcome to docs.opsview.com

Differences

This shows you the differences between two versions of the page.

opsview4.6:sharednotificationprofile [2014/09/09 12:19] (current)
Line 1: Line 1:
 +====== Shared Notification Profiles ======
 +Shared notification profiles allow an administrator to define notification parameters which other users can then use.
 +They are very similar in concept to [[opsview4.6:notificationprofile|notification profiles]], but these are shared and can be used by all contacts within the role.
 +
 +You will need to have [[opsview4.6:access|CONFIGUREPROFILES access]] to configure shared notification profiles. Remember - you need to have CONFIGURESAVE to save in the configuration screens!
 +
 +<note warning>
 +The list of objects that can be listed in the shared notifications profile page are based on the role of the profile, not the current user's role. We recommend you only allow administrators to use this functionality.
 +</note>
 +
 +If you have ADMINACCESS, you can see all shared notification profiles defined in the system, otherwise you will only see profiles associated to your own role.
 +
 +**Note**: You cannot share a notification profile across roles. This is because the list of objects accessible through the user's role may not match with the list of objects defined in the notification profile - this means  a shared notification profile could alert on different objects based on the user. Rather than have this confusion, Opsview limits the sharing of notification profiles to users in the same role.
 +
 +===== Name =====
 +Name for the notification profile. If a notification is sent from Nagios® Core using this profile, Nagios Core will say it was sent via a contact with the name of ''{contactname}/XX{name}''.
 +
 +This name must be unique.
 +
 +===== Role =====
 +This is the role associated with this profile. You cannot alter the role unless you have ADMINACCESS.
 +
 +===== Contacts =====
 +This lists all the contacts associated with this profile.
 +
 +===== Notify by =====
 +This is a list of all the active notification methods defined on the system. Choose the notification methods you would like to receive for the objects and filters below.
 +
 +By default, Opsview will ship with these active methods:
 +  * Email
 +  * AQL
 +  * RSS
 +
 +**Note**: If no method is selected, then the profile is effectively disabled.
 +
 +**Note**: If you select these methods, you still need to ensure that any relevant parameters are created in your contact profile. For example, emails will not be sent if your contact definition does not have the email variable associated. A warning is raised at Opsview reload time if there are missing variables.
 +
 +You can add more methods via [[opsview4.6:notificationmethods|Notification Methods]].
 + 
 +===== Selection of objects =====
 +The possible host groups, service groups and keywords listed depend on the [[opsview4.6:contact#access_objects|access objects of the role]].
 +
 +See the [[opsview4.6:access|access page]] for more information on how to select objects.
 +
 +The contact will need to have NOTIFYSOME access to have their notifications setup.
 +
 +==== Host groups ====
 +Select which host groups this notification profile will apply for.
 +
 +==== Service groups ====
 +Select which service groups this notification profile will apply for.
 +
 +==== Keywords ====
 +You can select which keywords this notification profile will apply for.
 +
 +**Note**: If a host or service is in multiple keywords, only one notification will be sent.
 +
 +===== Notify for Host On =====
 +For this notification profile, choose which notifications states will be sent. This acts as a filter to the host notification options.
 +
 +===== Notify for Service On =====
 +As above, but for services
 +
 +===== Notification Period =====
 +When notifications should be sent for this contact. Acts as a filter.
 +
 +===== Send From Alert =====
 +If set to 3, will only receive notifications from the 3rd notification onwards, based on the renotification interval.
 +
 +**Warning**: at least one notification needs to be sent before this value increments, otherwise no notifications will ever be received.
 +
 +===== Stop After Alert =====
 +
 +Alerts will cease being sent after this number of occurrences. The default is 0, meaning there is no limit to the number of alerts sent. Note that this is just for the sending of alerts — Opsview will still show the host or service in an unhandled state.
Navigation
Print/export
Toolbox