Documentation

Import and export Chronograf dashboards

Chronograf makes it easy to recreate robust dashboards without having to manually configure them from the ground up. Import and export dashboards between instances, or add dashboards as resources to include in a deployment.

Required user roles

All users can export a dashboard. To import a dashboard, a user must have an Admin or Editor role.

Task vs RoleAdminEditorViewer
Export Dashboard
Import Dashboard

Export a dashboard

  1. On the Dashboards page, hover over the dashboard you want to export, and then click the Export button on the right.

    Exporting a Chronograf dashboard

    This downloads a JSON file containing dashboard information including template variables, cells and cell information such as the query, cell-sizing, color scheme, visualization type, etc.

    No time series data is exported with a dashboard. Exports include only dashboard-related information as mentioned above.

Load a dashboard as a resource

Automatically load the dashboard as a resource (useful for adding a dashboard to a deployment).

  1. Rename the dashboard .json extension to .dashboard.
  2. Use the resources-path configuration option to save the dashboard in the /resources directory (by default, /usr/share/chronograf/resources).

Import a dashboard

  1. On your Dashboards page, click the Import Dashboard button.
  2. Either drag and drop or select the JSON export file to import.
  3. Click the Upload Dashboard button.

The newly imported dashboard is included in your list of dashboards.

Importing a Chronograf dashboard

Reconcile unmatched sources

If the data sources defined in the imported dashboard file do not match any of your local sources, reconcile each of the unmatched sources during the import process, and then click Done.

Reconcile unmatched sources


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: