What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

How can I change the defaults for names automatically generated for new SNMP sensors?



I would like to add new SNMP sensors to my SNMP device.

Can I influence the names that are automatically generated for the sensors?

name prtg sensor snmp

Created on Jul 29, 2010 3:17:33 PM by  Daniel Zobel [Product Manager]

Last change on May 6, 2019 11:57:44 AM by  Maike Guba [Paessler Support] (2,404) 2 1

9 Replies

Accepted Answer



This article applies as of PRTG 22

PRTG looks up names in the OID tree

To create names for new sensors on SNMP devices, PRTG scans an interface for available counters. At the respective OID address of a counter, there are usually several fields with descriptive information available. They are different for every device or OID. PRTG uses the information in these fields to name the sensors.

There is a standard set of fields that PRTG uses when it initially names sensors, but you can change it if you like. Of course, you always have the option to manually change a sensor name in a sensor's settings.

Changing the port name template

In a device's or group's settings, disable the inheritance of the SNMP Compatibility Settings. You can now change these settings. Navigate to the Port Name Template field.

The standard port name template is ([port]) [ifalias], which creates names such as (001) Ethernet1, for example. The actual values depend on your device.

You can use any field names that are available at a certain OID of your device, among which are:

  • [port]: The port number of the interface.
  • [ifalias]: The 'alias' name for the interface as specified by a network manager, providing a non-volatile handling.
  • [ifname]: The textual name of the interface as assigned by the local device.
  • [ifdescr]: A textual string containing information about the device or interface, for example, manufacturer, product name, version.
  • [ifspeed]: An estimate of the interface's current bandwidth (KBit/s).
  • [ifsensor]: The sensor type SNMP Traffic or SNMP RMON.

Combine them as you like to create suitable sensor names. Besides these field names in square brackets [ ], you can add other characters to the template for nicer formatting, such as space or brackets ( ).

Whether a field is actually available depends on the device you are scanning. If a field is empty or not available, PRTG adds an empty string to the name. This may even result in completely empty sensor names when you only use empty fields.


Created on Jul 29, 2010 3:30:48 PM by  Daniel Zobel [Product Manager]

Last change on Jan 4, 2023 2:50:38 PM by  Brandy Greger [Paessler Support]



It would be really really useful to be able to include the device name in the template.

Created on Aug 29, 2012 10:07:07 AM



Sorry, that is not possible, Templates only store sensor properties, and this is a device property.

Created on Aug 29, 2012 4:26:31 PM by  Torsten Lindner [Paessler Support]



OK, thanks.

Created on Jan 22, 2013 8:16:52 AM



We would really like to use placeholders for the devicenames.

For example we would like to change sensors names (ping 1) with multiple edit ( good option ) and change them to ping %device%

You can use these in email templates etc.... can you make the placeholders available in device names and templates.

Created on Jul 29, 2015 1:31:32 PM



That's an issue for us too, %device% would be a big win for us.

Created on Dec 19, 2016 9:52:04 AM



A general placeholder for all generated sensors using the device name would be very helpful. At the moment we will edit each sensor name - a frustrating work ;-)

Created on Jul 2, 2018 6:35:32 AM



Just wonder if apply this would effect application performance or not. Since we have enormous number of sensors to carry

Created on Sep 7, 2018 5:15:21 AM



Hi everyone,

This feature request has been converted into an official feature request:

Please read our new guide on how we want to handle feature requests in future. Thanks!

Kind regards,
Felix Saure, Tech Support Team

Created on Sep 7, 2018 1:06:17 PM by  Felix Saure [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.