Welcome to docs.opsview.com

Host template

Host templates contain a list of service checks. If a host has this host template associated with it, then it will inherit all the service checks from the host template.

Host templates are used to group common services together for association with a host.

You can layer on host templates, so that all services are combined together for the host. The order of these host templates is important because if a service check is duplicated in another host template, the first will be used.

The order is:

  • host specific monitors
  • host templates in the order assigned

If you want to see all the service checks that is associated to a host, click on the contextual menu for the host and select the number of service checks. This will resolve all the host templates.


You can change all related hosts via the host template edit page. Move hosts from the right hand side to the left hand box to create the association with the host template.

Note: if the smart host template removal option is enabled, host specific exceptions may be removed.


See the monitors page for more information about selecting the service checks that this host template would include for monitoring.

Management URLs

Management URLs are used to put extra entries onto the contextual menus for hosts using a given template.

Examples would be


If the SSH or Telnet contextual menu entries are clicked for a host in either the Hostgroup Hierarchy or the Host Edit List pages, the URL is passed to the broswer to act on (this assumes there are schemes set up to handle the URLs).

If two templates with the same ''Management URL' name are applied to a host, the first template in the list takes priority. The host template order is decided by the host configuration.

To add new handlers into Firefox, see http://kb.mozillazine.org/Register_protocol

To add new handlers into IE, see http://www.codeplex.com/UrlConf

Handling ssh requests with putty in Windows

For ssh: protocols in Windows, it is not so straight forward to setup. The problem is that the usual way for the protocol to be passed to the application in Windows is to send to the putty command with the parameter of ssh://, but putty does not recognise this and rejects with an error of:

Unable to open connection to 
Host does not exist

This is because putty is trying to resolve the name ssh:, rather than trying to access

Strangely, this works okay for telnet, because putty has code to strip off the telnet: part of the URL.

There are three options available (that we are aware of):

  • UrlConf will make the necessary registry setting changes. Requires .Net 1.1
  • CustomURL - similar to UrlConf. Requires .Net 2.0
  • Putup - Uses a putty: handler, instead of an ssh one. You will need to change the management URL to putty://machine=$HOSTADDRESS$. Be aware that:
    • putup installs its own version of putty. You will need to edit the registry settings if you want it to use a different copy of putty
    • This means there is a dependency that the browser user is using windows, so you probably want to setup an ssh://$HOSTADDRESS$ too for non-Windows users

It seems to us that the most obvious fix is for putty to be able to handle a parameter of ssh://address and strip off the ssh: part, as it already does this for telnet: