New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Wildcards in Sensor names?

Votes:

0

Your Vote:

Up

Down

Is in possible to use wildcards in sensor names?

We want our sensors to all include the name of the device to make identifying alerts and it would be a lot quicker to select all the Ping sensors for example and rename to "Ping %Server" than go through several hundred sensor names manually!

rename sensor wildcard

Created on Nov 6, 2015 12:00:44 PM by  Chris Parr (30) 1



1 Reply

Accepted Answer

Votes:

8

Your Vote:

Up

Down

This can be done using the PRTG API

Fitst create a list of all your PING sensors using the table.xml API call

/api/table.xml?content=sensors&output=xml&columns=objid,device,sensor&filter_type=ping

This will create a xlm result looking something like this:

   <item>
    <objid>2186</objid>
    <device>Cisco 1800</device>
    <sensor>Ping</sensor>
   </item>
   <item>
    <objid>2188</objid>
    <device>Alarm</device>
    <sensor>Ping</sensor>
   </item>
   <item>
    <objid>2190</objid>
    <device>CCTV</device>
    <sensor>Ping</sensor>
   </item>
   <item>
    <objid>2192</objid>
    <device>Cisco 2900</device>
    <sensor>Ping</sensor>
   </item>

You now have the objectID's of all your PING sensors with the name of their parent device.

Enumerating the XML result, use the rename API call to rename them to 'Ping Cisco 1800', 'Ping Alarm', 'Ping CCTV', ....

/api/rename.htm?id=2186&value=Ping%20Cisco%201800 
/api/rename.htm?id=2188&value=Ping%20Alarm 

Created on Nov 9, 2015 3:35:45 PM by  PRTG Tools Family [prtgtoolsfamily.com] (12,915) 3 4



Please log in or register to enter your reply.


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.