I have a group setup with the Sensor Management set to "Automatic device identification (standard, recommended)". How can I exclude a few IP addresses from this auto-discovery?
Thank you,
Joe
Article Comments
It's been a while since the last reply. Is there an update or a new way deal with this?
Jun, 2015 - Permalink
This hasn't changed due to a lack of interest from our customers to be able to exclude single IP addresses.
Jun, 2015 - Permalink
We are also interested in this feature. There should be a posibility to select/deselet devices by dns-name wildcards like hplj* or nb* or pc* So now the critical mass of customers is reached to implement this feature. :-)
May, 2016 - Permalink
We are also interested. Some devices on the network, like the first 10 in our multitude of blocks of IPs, I'd like to exclude. I also have a /25 at the beginning of one of those ranges that I am not supposed to monitor. I can try to create several lists to accommodate the exclusion of a few but it seems like a decent amount of work.
This is my use case: I am asked to monitor our resources in 10.61.64.0/18 but 10.61.64.0/25 does not fall under my jurisdiction (we can talk network design in another forum) as well as the first 10 IPs in each of those blocks. It'd be nice to include the 10.61.64.0/18 and exclude 10.61.64.0/25 and 10.61.64.128-.137, etc, etc, etc, etc, etc. for each block.
Thanks!
Jan, 2017 - Permalink
Hello harperfey,
thank you very much for your KB-Post.
I did just add your "vote" to the corresponding request to our Wish list! Thank you very much for the feedback! If you'd like, please have a look at the following blog post by our CEO, explaining "How We Rate Your Feature Requests".
Best regards,
Sven
Jan, 2017 - Permalink
May I also add that I would find it useful to be able to exclude blocks of IP addresses? We have a 172.16.24.0/22 network. We have blocks of addresses excluded from DHCP allocation for servers, switches, printers, wireless points,etc. The remaining ranges are used for client machines. I'd like to exclude client machines from PRTG monitoring.
Feb, 2017 - Permalink
Yes please. Having inherited an old network that was not designed (at all I think) there are all sorts of things everywhere. Part of the reason why I need a product like this...
Jan, 2018 - Permalink
To exclude systems from the auto-discovery group, try this: - configure auto-discovery not to re-discover systems that have already been discovered - for any systems you wish to ignore, remove the automatically created sensors, then optionally pause indefinitely with description so it doesn't get accidentally removed (and then re-discovered).
Feb, 2018 - Permalink
It's a pity that such a basic feature is not include... +1 to include this feature
Oct, 2019 - Permalink
Hey Marco,
please open a new Feature Request for this as described in this article.
Once we've received enough up-votes, we'll put it on our Roadmap.
Best regards,
Sven Roggenhofer [Paessler Technical Support]
Oct, 2019 - Permalink
The only way to not have IPs be within the Auto-Discovery when you set up a group would be to use the List of IPs and DNS Names option. That way you could specify the devices within the subnet you want to have auto-discovered. If you want to leave out a block of IPs from an Auto-Discovery group, then you would need to create two separate groups.
Within the Class C base IP with start/end (IPv4) option, there is no way to specify IPs that are outside of this Auto-Discovery.
Apr, 2013 - Permalink