Skip to content

Monitoring templates

Collection Zone stores performance configuration data in templates. Templates contain other objects that define where and how to obtain performance data, thresholds for that data, and data graphs.

You can define a template anywhere in the device class hierarchy or on an individual device.

Templates are divided among three types:

  • Device
  • Component
  • Interface

Creating templates

You can create an empty template to customize to your needs. To create a new template:

  1. Select ADVANCED > MONITORING TEMPLATES.

  2. Click the "add a monitoring template" button ("plus" icon, lower-left corner).

  3. In the Add Template dialog box, provide a name, and then choose a template path.

  4. Click Submit.

Copying templates

You can create a template by overriding an existing template. To override a template:

  1. Navigate to the template you want to copy.

  2. From the Action menu, select Copy/Override Template.

  3. In the Copy/Override dialog box, select the bound template to override

  4. Click Submit.

Renaming templates

To rename an existing template:

  1. Select ADVANCED > MONITORING TEMPLATES.

  2. Expand the organizer containing the template to be renamed, and then the class containing the template.

  3. From the Action menu, select View and Edit Details.

  4. In the Edit Template Details dialog box, enter a new name.

  5. Click Submit.

Template binding

The determination of which templates apply to what objects is called binding. Templates are bound in different ways, depending on the objects to which they are bound.

Device templates

Device templates are applied to devices, one to each device. The system employs a single rule to bind device templates to devices: the value of the zDeviceTemplates property. For most device classes, this is "Device".

Common device templates are:

  • Device
  • Apache
  • Active Directory
  • MSExchangeIS
  • MSSQLServer
  • IIS

For the Server/Linux/Apache device class, the zDeviceTemplates property might contain, for example, "Device" and "Apache". The system would collect CPU and memory information by using the Device template, and Apache-specific metrics by using the Apache template.

Binding a device template

To bind a device template to a device class or device:

  1. From the devices list, select a device class or device.

  2. On the Overview page, select Bind Templates from the Action menu.

  3. In the Bind Templates dialog box, use the arrows to move templates between the Available and Selected lists.

  4. Click Save.

Resetting bindings

Resetting template bindings removes all locally bound templates and uses the default template values. To reset bindings for a selected device or device class:

  1. From the Action menu, select Reset Bindings.

  2. In the Reset Template Bindings dialog box, click Reset Bindings to confirm the action.

Component templates

Component templates are named exactly according to the name of the underlying class that represents a component. For example,the FileSystem template is applied to file systems. Component templates can be applied multiple times to each device, depending on how many of the device's components match the template. Configuration properties do not control the application of component templates.

Note

Do not manually bind component templates.

Common component templates are:

  • FileSystem, HardDisk, IPService, OSProcess, WinService
  • Fan, PowerSupply, TemperatureSensor
  • LTMVirtualServer, VPNTunnel

Interface templates

Most interface templates are applied to network interfaces by using a special type of binding. Instead of using the name of the template's underlying target class, the system looks for a template with the same name as the interface type. You can find this type in the details information for any network interface.

For these standard interfaces when a Collection Zone cannot locate a template that matches the interface type, then it uses the ethernetCsmacd template.

Some vendors provide expanded monitoring capabilities on their interfaces. In some cases, ZenPacks provide custom templates specific to those types that can override this default behavior. A common example would be the Ethernet Interfaces interface type built to monitor these expanded capabilities for Cisco network interfaces. In this case the template's target class is used to bind the EthernetInterface template.

For more information about these expanded interface capabilities, refer to the Cisco Monitor ZenPack page.