Template Management

In Zebrix Control, a template is a configuration model applied to a category of equipment (a specific product type or product range).

Templates allow you to standardize configuration across multiple devices and maintain consistency within your fleet.

A template can include:

  • Driver configuration
  • Alert configuration
  • Incident configuration

Refer to the Equipments documentation for more details.

Creating a Template

To create a template:

  1. Go to Configuration > Templates
  2. Click on +
  3. Choose one of the following options:
  • Blank template: creates a template without any pre-existing configuration
  • From an existing device: copies the configuration of an already configured device
  • From another template: duplicates an existing template

When creating the template, fill in the following fields:

  • Default template: Indicates whether this template is marked as the default template.

⚠️ This flag is purely informational and has no automatic impact on devices.

  • Name: Name of the new template
  • Code: Internal template identifier
  • Product: Select the product range associated with this template

Applying a Template

Applying to a single device

  1. Go to the device configuration
  2. Click on Apply a template

You can also reapply a template from this screen if the template has been updated.

Applying to multiple devices

  1. Select the desired devices
  2. Click on Apply a template

Monitoring Template Application

In the device list, the Template column displays the template application status:

  • No template: No template is associated with the device
  • Up to date: The device configuration is synchronized with the template
  • Not applied: The template has been modified but has not yet been reapplied to the device
  • Modified: The device configuration has been manually changed and no longer matches the template

This allows you to quickly identify devices that are not compliant with the defined configuration model.

Dynamic Fields

Some drivers require parameters specific to each device (e.g., an IP address for a ping driver).

These values cannot be hardcoded in a template. Instead, dynamic attributes must be used.

For example, for a Ping driver requiring an IP address:

1. In the template configuration, use an attribute named ip, written as .

2. In each device configuration, add an ip attribute with its specific value.

Attributes:

  • Can be shared across multiple drivers
  • Can also be used outside of templates
  • Allow you to maintain a generic configuration adaptable to each device
Back to top