A word of caution
This post contains procedures that are not recommended by Paessler. Please note that we provide this information without warranty and that we cannot officially support you with this. Please make sure you keep a proper backup of your configuration and data files.
While it's not directly possible within PRTG, I have found a weird sort of workaround that probably doesn't work for every situation.
In my case, we've had problems with Windows network interfaces getting a new SNMP interface index when the server reboots and for some reason, PRTG doesn't recognize the change and either get's a "SNMP no such name" error or worse, starts putting one interface's data into another interface's sensor.
The process is: stop the core service, edit the "PRTG Configuration.dat" file and locate the sensor in question; change the index ID to the new one (learned through a manual snmpwalk process); save the file; restart the core service. Note: This only works if the old and new sensor are on the same device.
In essence, PRTG is now collecting from a "different" interface but still logging the data to the old sensor. I'm sure this process could be modified to move data from one device to another but that takes more XML-jitsu than I have.
Add comment