This page defines the contacts, or the users, of Opsview.
Be aware that some changes are immediately applicable:
- password changes (you will not be logged out)
- contact deletion means the user will not be able to use Opsview straight away
- some access rights do not require a reload
Everything else requires an Opsview reload to take effect.
This is the full name for the contact.
This is the username used for logging into Opsview. This must be unique
Note: The single sign-on system uses the username as the key, so if you change an existing user's username, this may cause problems.
Free text for this contact.
There are 5 default roles:
- Admin - can make administration changes to Opsview
- View all, change some - can see status for everything, but can only change a subset of hosts and services
- View some, change some - can only see status for a subset, but also have ability to change those
- View all, change none - can see everything and have no change ability
- View some, change none - can see specific items, with no change ability
See authorisation for more explanation of the access control.
You can also configure your own roles.
Note that if you save a new role for a contact, all this contact's notification profiles will have appropriate host groups, service groups or keywords removed if the new role does not allow access.
You can select a language for this contact. The web pages will be translated to reflect.
The list of languages is based on the translation files available.
The default option is to Use browser setting, which means the browser will send which languages it is willing to accept.
Opsview will fallback to English if your language does not exist.
More details can be found in the internationalisation page.
This popup is only available if there is more than one realm defined for authentication. Currently, only LDAP is supported.
There will also be an option for
local, which means the passwords will be stored in the Opsview configuration database.
For local users, you can set the initial password or reset it.
From Opsview 3.11.0, these are moved to the role configuration.
Under the notifications tab are a list of variables required based on the active notification methods.
These variables are required for the notification method to work correctly.
Below are common variables that may need to be entered, though the actual list is dependent on your system.
You can enter multiple email addresses by using a comma to separate the list.
This is the number used by SMS notification methods.
If you have problems receiving a notification, check:
- Your number is correct
- That the a notification was sent by Opsview
You may need to check further with your SMS system as there could be other reasons why the message was not sent. Be aware that SMS has no guaranteed delivery mechanism.
Opsview can provide notifications to used via an Atom feed (the RSS feed has been deprecated). The Atom feed is linked off every page (to http://opsview.example.com/atom).
Options for feeds include:
The maximum number of items to be listed in a feed at any one time
The maximum age (in minutes) an item will be in a feed before being removed
Should each object in the feed be updated (selected), or should a new item be added (unselected).
If this is on, that means that if a host goes from a DOWN state to an UP state, only the UP state will be in the feed because it is the latest state for that object.