<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Create Device Template

If you want to add a certain device several times, you can create a device template from an existing device in your device tree. When creating a device template, PRTG saves information for nearly all sensors on this device to a template file that you can later use in combination with Auto-Discovery (restrictions apply for a few sensors). Custom device templates are also available in the PRTG Script World.

From the sensors, all relevant settings are saved, except settings that refer to other objects, such as schedules, notification triggers, and access rights. PRTG automatically reverts them to Inherit.

To start, right-click a device in your device tree. From the context menu, select Create Device Template.... An assistant appears.

Create Device Template Assistant

Create Device Template Assistant

icon-i-roundDevice templates only save the sensors on the device and the sensors' settings, including channels. The device itself and its settings are not saved. For successful device template creation, sensors must be added to the device (either manually or via Auto-Discovery) and must be device template-capable.

Device Template Settings

Choose Template Name

Template Name

Enter a meaningful display name for the template as it appears in the web interface.

Exclude Sensors

Select sensors that you want to exclude from the device template. Mark the corresponding check boxes of the sensors that you want to exclude from the device template.

icon-i-roundSensors that cannot be saved into templates do not appear in this list.

icon-i-roundSensors that dynamically scan for available monitoring items when you add the sensor to a device do not appear in this list. PRTG automatically includes these sensors in the template if they support the template functionality. You cannot exclude these sensors from the device template.

icon-i-round-redSave your settings. If you leave the current page, all changes to the settings are lost.

If your template file was saved successfully, you see an according message and can review the sensors that were added. Click OK to finish. The device template is now stored in the program path of your PRTG core installation. Your device template file contains all sensors, including their settings, of the original device.

During your next auto-discovery, choose the Automatic sensor creation using specific device templates option and select the name of your newly created device template from the list. PRTG then tries to discover the stored sensors on the new (or existing) device. If the physical device answers to a sensor request, the sensor is added to the PRTG device.

icon-book-arrowsFor detailed information, see section Auto-Discovery.

Settings That Are Not Saved

There are a few settings that you cannot save into a device template, so PRTG sets them to default, for example:

  • The Dependency Type setting Master sensor for parent (in Schedules and Dependencies section)
  • Result Handling setting Write result to disk because this is intended for debugging purposes only.
  • Settings in the Access Rights section are not saved to avoid security flaws.

icon-i-roundIn general, you cannot save all Sensor Settings and Sensor Channel Settings (for example, channel limits of dynamically created channels) of sensors that dynamically scan for available monitoring items when you add the sensor. This affects, for example, traffic sensors where you can choose interfaces that you want to monitor in the Add Sensor dialog.

Furthermore, because of internal restrictions, the following sensors are not saved into a device template:

  • Amazon CloudWatch Alarm
  • Amazon CloudWatch EBS
  • Amazon CloudWatch EC2
  • Amazon CloudWatch ElastiCache
  • Amazon CloudWatch ELB
  • Amazon CloudWatch RDS
  • Amazon CloudWatch SNS
  • Amazon CloudWatch SQS
  • Business Process
  • Cluster Health
  • Core Health
  • DHCP
  • DICOM Bandwidth
  • DICOM C-ECHO
  • DICOM Query/Retrieve
  • Docker Container Status
  • Dropbox
  • Enterprise Virtual Array
  • Exchange Backup (PowerShell)
  • Exchange Database (PowerShell)
  • Exchange Database DAG (PowerShell)
  • Exchange Mail Queue (PowerShell)
  • Exchange Mailbox (PowerShell)
  • Exchange Public Folder (PowerShell)
  • Google Analytics
  • Google Drive
  • HL7
  • HTTP IoT Push Data Advanced
  • IPFIX
  • IPFIX (Custom)
  • IPMI System Health
  • jFlow V5
  • jFlow V5 (Custom)
  • Microsoft OneDrive
  • MQTT Round Trip
  • NetApp Aggregate
  • NetApp I/O
  • NetApp LIF
  • NetApp LUN
  • NetApp NIC
  • NetApp Physical Disk
  • NetApp SnapMirror
  • NetApp System Health
  • NetApp Volume
  • NetFlow V5
  • NetFlow V5 (Custom)
  • NetFlow V9
  • NetFlow V9 (Custom)
  • Packet Sniffer
  • Packet Sniffer (Custom)
  • Probe Health
  • QoS (Quality of Service) One Way
  • QoS (Quality of Service) Round Trip
  • REST Custom
  • REST Dell EMC Capacity
  • REST Dell EMC File System
  • REST Dell EMC LUN
  • REST Dell EMC Pool
  • REST Dell EMC System Health
  • Sensor Factory
  • sFlow
  • sFlow (Custom)
  • SNMP Trap Receiver
  • Syslog Receiver
  • System Health
  • WMI Security Center

No Update of Device Templates

Once a device template has been created, it is not possible to add additional sensors to it via the PRTG web interface. If you want to create a template with an extended set of sensors, create a new template.

icon-i-round-redWhen saving a new device template, all internal IDs of the sensors in this template are updated. Because of this, when you apply a new template to an existing device, PRTG newly creates all sensors that this template contains on this device, even if these sensors were previously created using another device template!

icon-i-roundYou cannot directly delete device templates.

icon-prtg-on-demandYou cannot edit existing template files on PRTG hosted by Paessler.

More

PRTG Manual:

 

Ajax Web Interface—Advanced Procedures—Topics

Other Ajax Web Interface Sections

Keywords: Device,Device Template