I have looked in the knowledge base but have not found a solution for this, and it happens quite often. I understand that if a device reboots the cisco snmp health sensor might be given a different id. PRTG will stop monitoring that sensor and show it as red (critical). Pausing and restarting the sensor, or restarting PRTG does not fix the issue. So, you have to add the sensor again. So now you have one sensor red, and one sensor green, but the "new" sensor does not have all the history of the old sensor that is now red and in alarm. It looks like if you want to keep the history of the "bad" sensor, all you can do is pause it indefinatley so you don't have a sensor in alarm, but can go back and look at the history. I have yet to see a knowledge base article that tells you how to sucsessfully move the historic data to the duplicated sensor. Just wondering if their may still be a way, or if this will be an enhancement for a future release. Thank you.
Copy historic data from sensor on same device that is a duplicate
Votes:
0
1 Reply
Votes:
0
Hello there,
It's not possible I'm afraid as the sensor data is not stored per sensor but per device like this in folder "Monitoring Database":
- folder for particular day
- data file of device 1
- data of sensor 1
- data of sensor 2
- data file of device 2
- data of sensor 1
- data of sensor 2 etc.
- data file of device 1
It's not possible to extract data for one particular sensor from a device's sensor data file and put into another device's historic data file.
Kind regards,
Erhard
Created on May 16, 2018 11:24:20 AM by
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.
Add comment