Hi all,
how can I move the device to another map without losing their history data?
In old version 3.6 its work correctly by copy / paste. This function does not work in version 6.36 (the object is placed on the same map). In version 6.35.4 this works, but historical data are removed.
I need to split too complicated map on two separate maps.
There was a change in 4.b3 where when you click the copy button history data is cleared, it is also a bug since it clears the history of the original object. It would be nice if “copy” gave a popup to keep history or delete it. Also removed was the RRD editor, if you placed a graph on a chart you could go into advanced properties and see the actual RRD data, If they still at least had that you could manually add graphs to charts and copy data between graphs.
Oops…
For what purpose, it can be used copy / paste? Does it have any practical use?
Data sources are OK, I need to move objects as routers, servers, printers, etc. including the history of their services (ping, http, ftp, dns, etc.).
It got some bad luck, huh?
In v6 builds at the moment there are no way to move devices between maps without losing the historical date of the monitored device. When we finish work on server side cli, then adding one and the same device to multiple maps will be much easier task.
There is still no way to move an object to another map? Or at least preserve historical data during the copy / paste?
I need to “clean up” my too complex maps…
It would be really nice if it was designed so that the devices themselves were their own entities with their own unique identifier. They could do their own polling and monitoring on the device itself. Then you could just drop a reference to that device on the map, remove the reference on the map, or even drop the reference on more than one map but they would all just reference the device entity itself. This way you wouldn’t lose history unless you actually deleted the device itself. Also if you dropped a reference on more than one map, it wouldn’t poll or run notifications multiple times because that would be handled on the actual device itself.