Is there a standard procedure when transferring dashboards between DataMiner Systems?
We are, currently, looking at the possibility of reusing dashboard as we move through integration phases (Development -> Staging -> Production). However, it has been noticed that when a dashboard is transferred between DataMiner Systems, it needs to be re-configured after the fact for it to become functional.
Initial observations point to inconsistencies in element IDs, but we would like to know if there are a set of rules we should follow when building dashboards in order to make sure they can be transferred from DMS to DMS while preserving full functionality
Thank you in advance,
Hi Rene,
Dashboards can indeed hold references to other objects like elements, services, views, ... The references are stored on id to allow renaming of the objects.
Transferring dashboards from one cluster to another (e.g. via Catalog, solution packages with dashboards, ...) is a use case we are definitely looking into. At this stage, we believe that storing references by id still makes sense, so we might add migration steps that convert from id -> name and name -> id when adding/installing dashboards to/from the solution/catalog.
Please let me know if that makes sense to you.