Documentation

Configuration of monitoring accounts

On the page

Need some help?

Introduction

Monitoring accounts are required for the successful execution of ServiceNav services. For example, a monitoring account of the SNMP Community type will allow information to be collected about the target host via the SNMP protocol.
This procedure explains how to use monitoring accounts in the configuration or reconfiguration of monitoring.
This feature is accessible from the user interface by navigating to Configuration > General > Monitoring Accounts.

General principles

Definitions

Monitoring accounts are required for the successful execution of ServiceNav services. For example, a monitoring account of the SNMP Community type will allow information to be collected about the target host via the SNMP protocol.

Monitoring accounts are defined for each service. The goal within ServiceNav is to define a monitoring account only once, at company, site or host level. Once services are defined for a device, ServiceNav then automatically configures the services using the information provided at the monitoring account level.

The ability to set an account different from the account defined at company level is retained. To do so, the user will be able to modify the account at the level of a site, a host, or a service.
Such monitoring accounts are protected: any modification of a monitoring account at a higher level in the hierarchy (company ⇒ sites ⇒ host) will not override the configuration of such monitoring accounts.

The account types are as follows:

The information required depends on the type of account. For example, for an account of the type 'Windows - Admin', the domain (optional), the user and the password must be provided.

Inheritance rules

Monitoring account information is defined at company level, site level, host level, or service level.

If a monitoring account is updated at company level, ServiceNav will update all services of all hosts at all sites under that company, except those marked as protected either at site, host or service level.

If a monitoing account is updated at a site level, ServiceNav updates all services for all hosts at that site and subordinate sites, except those marked as protected at the host or service level.

Monitoring account protection covers all the fields of the account (example for a Windows account, the domain, account name and password are protected).

A service is configured with a single monitoring account: there is no service that requires multiple monitoring accounts.

If a user wants a specific configuration applied to a service, The monitoring account information must be supplied on the configuration page of the service.

Deployment Recommendations

We recommend,at the beginning of deployment, defining monitoring accounts at company level, then at site level, and finally at host level if exceptions are necessary.

Then, in the event of a subsequent change of password for a monitoring account, a simple modification of this account defined at the highest level in the company/site hierarchy will be propagated to all the hosts at all the sites that need it.

Configuration pages for monitoring accounts

Company, site

Monitoring accounts are defined at company or site level. To access the configuration:

  • Navigate to Configuration > General > Monitoring Accounts.
  • Select the company or site in the company tree.

Monitoring Accounts

Status the padlock-lock symbol indicates that the monitoring account is protected at this site. The Open padlock symbol indicates that the monitoring account is defined and protected at a site higher up the tree structure.

Type indicates the type of monitoring account.

Company : indicates the site or company at which the monitoring account is protected.

Values indicates the details of the monitoring account. Passwords are hidden.

Description A description of the monitoring account.

From this list, you can :

  • Protect or unprotect a monitoring account by clicking on the symbol in the column, Status
  • Change the values of a supervision account by clicking on the symbol in the column Status or on the column Type

Hosts

Monitoring accounts are set at hostlevel. To access the configuration:

  • Navigate to the menu Configuration > Hosts> List
  • Select the company or site in the company tree
  • Open the specific host configuration details by clicking on the host in the list.
  • Click on the tab, Accounts

Equipment - accounts tab

The Closed padlock symbol indicates that the monintoring account is protected at the host level.

The Open padlock symbol indicates that the monitoring account is defined and protected at the level of the site associated with the host in the tree structure, or a site/ company higher in the hierarchy. By clicking on the account, the site/ company at which the account is defined is displayed:

Equipment - accounts tab

The red padlock symbol indicates that a service deployed against the host requires a monitoring account to be configured at the host, site or company level, if this account is not defined and protected at the service level.

From this page, you can modify the monitoringaccount at the hostlevel (protect/ unprotect it, change its values) by clicking on the account :

Equipment - accounts tab - modification

Service

Monitoring accounts are defined at the level of the service. To access the definition :

  • Navigate to Configuration > Services > List
  • Select the company or site in the company tree
  • Open the service configuration page by clicking on the service in the list.
  • Click on the tab, Availability and checks

Unit Service - Unprotected Supervisory Account

On this page, if the account is not protected, the account information is not visible. Otherwise, they are visible and editable.

Unit Service - Protected Supervisory Account

Scenarios

Adding a monitoring account at company or site level

  • Navigate to Configuration > General > Monitoring accounts.
  • Select the company or site in the company tree.
  • Click Add.

Company - supervisory accounts

  • Select the account type from the drop down list (account types already defined are not shown in this list)

Company - Supervisory Accounts - addition

  • Enter the requested values and click on Validate. The defined account type is immediately propagated to the unit services of the company's equipment and subordinate sites.

Modification of a monitoring account at company level

To change the monitoring account information :

  • Navigate to Configuration > General > Monitoring accounts.
  • Select the company code in the company code tree.
  • Click on the monitoring account to be changed (column Type).
  • Modify as desired and click on Apply.
  • A warning message states: "These updates will be applied to the unlocked monitoring accounts for the sites and the hosts. Do you want to continue?". Click on Yes.

Modification of a monitoring account at a site level

To change the monitoring account information :

  • Navigate to Configuration > General > Monitoring accounts.
  • Select the company code in the company code tree.
  • Click on the monitoring account to be changed (column Type).
  • Modify as desired and click on Apply.
  • A warning message states: "These updates will be applied to the unlocked monitoring accounts for the sites and the hosts. Do you want to continue?". Click on Yes.

To protect a monitoring account already defined at company level :

Supervision accounts - surcharge

  • Navigate to Configuration > General > Monitoring accounts.
  • Select the site in the company tree.
  • Click on the symbol next to the monitoring account to be changed (Status column).
  • Click Yes , enter the account information, then click on Apply :

Supervision account - surcharge - modification

  • A warning message states: "These updates will be applied to the unlocked monitoring accounts for the sites and the hosts. Do you want to continue?". Click on Yes.

If you no longer wish to protect a monitoring account defined at site level, that is, to use the monitoring account defined at a higher site in the tree structure, or at company level, you must delete the account defined at site level.

 

Deletion of monitoring accounts at company or site level

To delete one or more monitoring accounts :

  • Navigate to Configuration > General > Monitoring accounts.
  • Select the company code in the company code tree.
  • Select the monitoring account(s) to be deleted.
  • Click on the trash button.

Supervision accounts - deletion

  • A confirmation window is displayed. This window indicates which accounts can and cannot be deleted.

Supervision account - deletion - confirmation

It is not possible to delete accounts currently used by one or more services, and for which no monitoring account is found in a higher company or site level.

It is possible to delete accounts used by one or more services, and for which a monitoring account of the same type is found in a higher level site or company.

It is possible to delete accounts if they are not used by any service.

  • Click Apply to proceed with the deletion of the indicated accounts, or on Cancel to abandon the delete action.

 

Adding a monitoring account at host level

navigate to the hosts configuration page, and click on the Accounts tab. Accounts.

This tab contains the accounts required for all the services associated with the host: it is therefore not necessary or possible to manually add monitoring accounts at this level.

Modification of a monitoring account at host level

The information that can be modified is as follows:

  1. Change an account from "unprotected" to "protected": in this case, the information associated with the account becomes editable, and the fields are empty.
  2. For protected accounts, information may be edited.
  3. Switch an account from "protected" to "unprotected" (by clicking on the radio button).

To modify a monitoring account at the host level :

  • Navigate to Configuration > Hosts > List.
  • Select the company or site in the company tree.
  • Open the host configuration page by clicking on the host in the list.
  • Click on the tab, Accounts.

To change an account from "unprotected" to "protected" :

  • Select the account on the left side.
  • Select Yes : the values associated with the monitoring account are reset.
  • Fill in the values associated with the monitoring account.
  • Click Apply.

Equipment - accounts tab - modification

To change the information associated with a protected account :

  • Select the account on the left side.
  • Fill in the values associated with the monitoring account.
  • Click Apply.

 

To change an account from "protected" to "unprotected":

  • Select the account on the left side.
  • Select No : a monitoring account of the same type is displayed.
  • Click Apply.

Equipment - accounts tab

The account of the same account type is the one defined at host site level, if it exists, or at the first company/site level up the company tree.

If no account of the same type is found at the host site, or at a higher level site, or at the company level, it will not be possible to set the monitoring account unprotected: it will first be necessary to define a monitoring account at the site or company level.

Equipment - Accounts - Cannot be changed

Deletion of a monitoring account at host level

The monitoring accounts defined at the host level are those required by the services associated with the host: it is therefore not necessary to manually delete monitoring accounts at this level.

When a service is deleted from a host, the associated monitoring account no longer appears in the host configuration master record (tab Accounts).

Adding hosts

A host can be added from discovery or manually from the host list page.

During discovery, the SNMP community and a Windows administration account are pre-populated with accounts of the same type defined at the site level (or failing that, at a parent site or company level):

Census - supervisory accounts

The following rules apply when adding a device discovered using an SNMP community and a Windows administration account: If the monitoring account (SNMP, WMI) entered in during discovery is identical to a monitoring account for the site associated with the device, or in a parent company/site, the monitoring account (SNMP, WMI) is not protected at the host level. Otherwise it is protected.

On the host discovery page, the monitoring accounts used to poll the host can be seen by clicking on the host in the discovered hosts list :

Census - Supervision Accounts - Display

Whether from discovery or from the hosts list, adding a host requires defining host templates for that host.

Once the host has been added, you must complete the configuration by going to the host configuration page, tab Accounts.

Equipment - Accounts - not configured

Accounts with a red padlock must be set up and protected, or an account of the same type must be added at company/site level.

Adding host templates to a host

The addition of one or more host templates to a host implicitly assigns services to this host: the configuration must be confirmedby clicking on the tab Accounts.

Equipment - Accounts - not configured

Accounts with a red padlock must be set up and protected, or an account of the same type must be added at company/site level.

 

Adding a service to a host

From the services list, adding a service to a host involves checking the configuration of the service in the hosts Accounts tab.

In this example, the IBM-AS400-Cpu service is added to a host.

Unit services - IBM-AS400-CPU addition

The Accounts tab in the host configuration page shows that the AS400 monitoring account should be defined at either the service, host, site or company level.

Equipment - accounts - AS400 addition

 

Checking the configuration

To check the configuration :

  • Navigate to Configuration > General > Loading.
  • Select the company code or site in the company/site tree.
  • Select the monitoring box for which you wish to check the configuration.
  • Click Apply.

The document Detail of configuration errors describes the list of errors which may be encountered.

Supervision account - configuration generation - error

This may also be of interest to you

Mass import and update

Using ServiceNav WebServices

Create companies and sites

en_US
fr_FR en_US

Welcome to ServiceNav!

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

[COVID - 19 ] - TELEWORKING, TARGET AVAILABILITY 100% !

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.