Hello

Normally I add a device with device name and a DNS Name do the PRTG System. After auto-discovery with a template the device name will be renamed to DNS Name(Device Name). Following sensors will be added with the template to the device: SNMP CPU Load SNMP Disk Free SNMP HP Proliant System Health SNMP Memory SNMP System Uptime

As example: Device Name: SERVER1 DNS Name: Server1.local.net

After auto-discovery: Device Name: SERVER1.local.net(SERVER1)

Is it possible to change this behavior? Thank you

Article Comments

There is currently no way to disable this from happening, PRTG will automatically change the name to the name that is in DNS with the original name in brackets (). If you change the name afterwards and run another Auto-Discovery it will not be changed but on the first Auto-Discovery it does this automatically.


Feb, 2014 - Permalink

That is VERY disappointing. I've been manually entering hundreds of devices on public IPs and it is pulling the reverse dns record (which is like 208-122.122.122.t3com.net) and adding it to the name. This makes it VERY hard to know what email notifications are about by the subject because it's so long. There has to be a way around this... or a script to change the names back?


Mar, 2014 - Permalink

There isn't a way to change this behavior with PRTG but you could program a script to use the API to change the names of the objects. You can see the call to the API under Setup->PRTG API->Object Manipulation.


Mar, 2014 - Permalink

I have the same problem. That is really disappointing. Hopefully that will be changed in a future version!


Feb, 2017 - Permalink

Same here, I would like to keep the names of the devices as i set them. will there be a possibility in the future to keep them pre-configured?

Thanks.


Nov, 2017 - Permalink

You can only avoid that by moving the device out of the auto discovery group and configure the auto discovery directly on the device (rather than it being dependant on the group discovery settings).

As of right now, it's not planned to change this behaviour. Sorry!

Kind regards,
Stephan Linke, Tech Support Team


Nov, 2017 - Permalink

This is typical response from Paessler and it's terrible - that's the way it is and we don't care. Why even bother having us give the device a name if you're going to rename it?


Jul, 2018 - Permalink

Hi Kyle,

I understand that you're dissatisfied with the way we handle stuff like this. The thing is that Auto Discovery groups always rename the hosts according to the lookup DNS name it can retrieve. In order to avoid it and keep the names you give them, move them out of the auto discovery group and configure the auto discovery on a per devices basis.

Kind regards,
Stephan Linke, Tech Support Team


Jul, 2018 - Permalink

Hi Stephan,

I have tried to follow your advice however creating them with no autodiscover and then running it after it has created still renames the device. Having just rolled out 850 printers with a carefully crafted api query only to have my names like "STH-Printer1" replaced with "CND453452-Local.ASNet134.STBN.printers" is somewhat saddening i gotta say and the idea of regexing them back to rights is enough to make a man resign :)


Dec, 2018 - Permalink

Hey Sam,

For that amount of printers, it's probably easier to use PRTGapi to create the device according to a CSV and have it named accordingly. You could also pass the corresponding device template to trigger a automatic sensor discovery to them afterwards :)

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team


Dec, 2018 - Permalink