On this page:
You can export and import custom dashboards and custom dashboard templates interactively from the Controller UI using the procedure described here or programatically using a special REST API
The export operation creates a JSON file, which you can then import to another controller.
See Configuration Import and Export API for information on importing and exporting custom dashboards and dashboard templates programmatically.
Do one of the following:
If you have edit permissions for dashboards, you can use either method. If you do not have edit permissions, use the Export option from the custom dashboard list.
The dashboard is exported to a file named CustomDashboard_<dashboard_name>_<unique_id>.json.
You can optionally rename this file before you import it.
Importing and exporting are for re-using the template in an different application or a different controller. If you want to use the template in another tier or node in the same application you do not have to export and import it. You can simply associate it. See Associate a Custom Dashboard Template with a Tier or Node in Create and Manage Custom Dashboards and Templates.
The import operation places the custom dashboard into the proper location for use by the controller into which you are importing.
If the metrics, nodes, tiers, or applications used in the exported dashboard do not exist in the new controller environment, warning messages are displayed.
The warnings look like this:
Even when the metrics are not available in the new controller environment, your import succeeds and preserves the widgets and layout of the dashboard. You can modify the widget properties substituting different metrics to create a similar-looking dashboard in the new environment.