I have 100+ remote probes, 85 of them are connected over a WAN and 15 are connected locally to the same LAN as the core ( master\secondary) or with high speed links.

When I do an auto upgrade, bi-monthly ( so 6 times a year or more) The update process takes a very long time to complete due to the number of remote probes and the WAN connections.

The problem is my environment that the 15 remote probes I have that are local could be upgraded and back online in a fraction of the time it takes the other 85 to complete the process. But of course they sit there some of them as long as the probes which are 3000km away. The 15 high priority probes have 45% of the total sensors; so monitoring data is lost unnecessarily and the blackout window is much larger than is need be.

I would like a way to could set the order or priority of a remote probes auto update. I don't need to set the specific order but I do need to set a way to identify what priority group of the remote probes should belong too and higher priority be auto updated first. Normal / High / Low perhaps.

Article Comments

You can only set the amount of remote probes that are updated at the same time:
How can I change the number of remote probes updated simultaneously?

Then only two remote probes are updated concurrently, saving you some bandwidth. The update process might take a bit longer however :)


Aug, 2015 - Permalink

Hi,

Bandwidth management isn't the reason I ask. Some of the my probes (15) should be updated before others (85) to get the best monitoring experience and reduce the impact an update of the remote probes.

I would like to request two features I believe will enhance the auto update feature;

1 - Ability set an auto update priority to a probes settings.

2 - Ability to set the auto update host to come from either the primary or the secondary Core server instead of the default primary.

For #2 now that remote probes connect to both core servers, this opens the door for auto updates to come from both servers at once. Allowing geographically disbursed deployments to better make use of the WAN connections.

I think both 1 and 2 compliment each other and also build on the new dual connection remote probe feature you recently added.


Aug, 2015 - Permalink

The request is absolutely legit, but so fare you are the first on to request this, so it is unlikely that you will see this in PRTG any time soon, sorry.


Aug, 2015 - Permalink

Any update on this request? Has any improvement been made in this area outside of the specifics of this requests that you can share?

This feature would still be very useful for us.

Thank you


Apr, 2016 - Permalink

@stephensuley: No such functionality is implemented in PRTG. There are also no plans to do so in future currently.
Best regards


Apr, 2016 - Permalink