|Name||Dashboards data migration|
With the increasing relevance of the historical statistic data generated by the ThinkServer monitors, a new step has to be taken into account during the migration of the whole monitoring environment in order to keep the old data and generate the new data in a consistent way.
Bear in mind that performing the typical installation and migration steps will make the data generated by the old-ThinkServer invisible and won't be available in Dashboards.
Keep the old data generated by the old-ThinkServer and generate the new data from the new-ThinkServer in a consistent way, so that all data can be accessed from Dashboards without any loss.
Note that this is actually an issue only when the ThinkServer Engine is migrated into a new machine. An SQL Server change is not relevant in this scenario, as we should attach the old DataBases files to the new SQL Server and change the ODBC DSN in the new-ThinkServer machine.
Performing the typical ThinkServer installation and monitor migration steps will make the old data generated by the old-ThinkServer invisible. The reasons are the following:
The new generated data by the imported monitors in the new-ThinkServer is created with a new set of TSUID, Host IDs, Script IDs, Chart IDs, Variable IDs.
When displaying the Statistical data in Dashboards, only the new data genereted by the new monitors will be shown in the dashboards and tables. Even if the Statistics DB contains the old-ThinkServer data, Dashboards won't be able to show it as all identifiers have been changed in the new-ThinkServer.
To migrate the old Statistics data generated in the source ThinkServer and make it available on the new environment, several steps must be performed:
Please, check the Configuration of a monitor to deepen on the reasons of this methodology.
Still have questions? We can help. Submit a case to Technical Support.