I have several sensors that show an error connecting to a virtual machine. The virtual machine was a Hyper v machine that was recreated after some corruption. The newly created server has the same ip address and same dns name. However some of the sensors in PRTG do not connect via WMI anymore. An example might be the CPU sensor or the Hyper V network adapter.
So how can I get the PRTG core server to start pulling data again from this server? The key is to not lose historical data. So I don't want to add a new device. And some of the sensors did start back up automatically.
Is there a way to edit the sensor to modify whatever might have changes on the server? Like the name of the hyper v adapter? Or can I add a new sensor and then change the id to match the old sensor?
Hi CastleWorldWide,
The WMI sensors directly point to the selected interface name which was marked while creating the sensor. If this adapter changes, it will require a new sensor in PRTG, basically, it's a new adapter. You can keep the historic data by pausing the old sensors, this will allow you to run reports in the future, but it will not be possible to merge the historic data of the old sensors and the data of the new sensor, nor to change the interface after the sensor was created.
Best regards, Felix
Feb, 2017 - Permalink