2016-10-21 04:01:34 -05:00
+++
2020-10-01 16:13:39 -05:00
title = "JSON model"
2016-10-21 04:01:34 -05:00
keywords = ["grafana", "dashboard", "documentation", "json", "model"]
2020-10-01 16:13:39 -05:00
aliases = ["/docs/grafana/latest/reference/dashboard/"]
weight = 1200
2016-10-21 04:01:34 -05:00
+++
2015-11-02 01:17:23 -06:00
2020-10-01 16:13:39 -05:00
# Dashboard JSON model
2015-11-02 01:17:23 -06:00
2018-02-08 02:55:12 -06:00
A dashboard in Grafana is represented by a JSON object, which stores metadata of its dashboard. Dashboard metadata includes dashboard properties, metadata from panels, template variables, panel queries, etc.
2015-11-02 01:17:23 -06:00
2015-11-02 01:53:24 -06:00
To view the JSON of a dashboard, follow the steps mentioned below:
2015-11-02 01:17:23 -06:00
2015-11-02 01:53:24 -06:00
1. Go to a dashboard
2020-10-01 11:45:05 -05:00
1. Click on `Manage dashboard` menu on the top navigation bar
1. Select `View JSON` from the dropdown menu
2015-11-02 01:17:23 -06:00
2015-11-02 02:21:59 -06:00
## JSON fields
2015-11-02 01:17:23 -06:00
2015-11-02 01:53:24 -06:00
When a user creates a new dashboard, a new dashboard JSON object is initialized with the following fields:
2020-09-30 14:45:07 -05:00
> **Note:** In the following JSON, id is shown as null which is the default value assigned to it until a dashboard is saved. Once a dashboard is saved, an integer value is assigned to the `id` field.
2015-11-02 01:17:23 -06:00
2017-10-05 12:01:03 -05:00
```json
2015-11-02 01:17:23 -06:00
{
"id": null,
2018-02-08 02:55:12 -06:00
"uid": "cLV5GDCkz",
2015-11-02 01:17:23 -06:00
"title": "New dashboard",
"tags": [],
"style": "dark",
"timezone": "browser",
2015-11-02 01:53:24 -06:00
"editable": true,
2015-11-02 01:17:23 -06:00
"hideControls": false,
2016-12-14 07:33:33 -06:00
"graphTooltip": 1,
2018-02-08 02:55:12 -06:00
"panels": [],
2015-11-02 01:17:23 -06:00
"time": {
"from": "now-6h",
"to": "now"
},
"timepicker": {
2015-11-02 02:21:59 -06:00
"time_options": [],
"refresh_intervals": []
2015-11-02 01:17:23 -06:00
},
"templating": {
"list": []
},
"annotations": {
"list": []
},
2018-05-08 14:25:45 -05:00
"refresh": "5s",
2018-08-20 08:33:49 -05:00
"schemaVersion": 17,
2015-11-02 01:17:23 -06:00
"version": 0,
"links": []
}
```
2015-11-02 01:53:24 -06:00
Each field in the dashboard JSON is explained below with its usage:
2020-09-30 14:45:07 -05:00
| Name | Usage |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| **id** | unique numeric identifier for the dashboard. (generated by the db) |
| **uid** | unique dashboard identifier that can be generated by anyone. string (8-40) |
| **title** | current title of dashboard |
| **tags** | tags associated with dashboard, an array of strings |
| **style** | theme of dashboard, i.e. `dark` or `light` |
| **timezone** | timezone of dashboard, i.e. `utc` or `browser` |
| **editable** | whether a dashboard is editable or not |
| **graphTooltip** | 0 for no shared crosshair or tooltip (default), 1 for shared crosshair, 2 for shared crosshair AND shared tooltip |
| **time** | time range for dashboard, i.e. last 6 hours, last 7 days, etc |
| **timepicker** | timepicker metadata, see [timepicker section ](#timepicker ) for details |
| **templating** | templating metadata, see [templating section ](#templating ) for details |
| **annotations** | annotations metadata, see [annotations section ](#annotations ) for details |
| **refresh** | auto-refresh interval |
| **schemaVersion** | version of the JSON schema (integer), incremented each time a Grafana update brings changes to said schema |
| **version** | version of the dashboard (integer), incremented each time the dashboard is updated |
| **panels** | panels array, see below for detail. |
2015-11-02 02:21:59 -06:00
2018-02-21 03:47:14 -06:00
## Panels
2015-11-02 02:21:59 -06:00
2019-09-19 17:04:56 -05:00
Panels are the building blocks of a dashboard. It consists of data source queries, type of graphs, aliases, etc. Panel JSON consists of an array of JSON objects, each representing a different panel. Most of the fields are common for all panels but some fields depend on the panel type. Following is an example of panel JSON of a text panel.
2015-11-02 12:15:40 -06:00
2017-02-07 00:48:01 -06:00
```json
2015-11-02 12:15:40 -06:00
"panels": [
2018-02-21 03:47:14 -06:00
{
"type": "text",
"title": "Panel Title",
"gridPos": {
"x": 0,
"y": 0,
"w": 12,
"h": 9
2015-11-02 02:21:59 -06:00
},
2018-02-21 03:47:14 -06:00
"id": 4,
"mode": "markdown",
"content": "# title"
}
2015-11-02 12:15:40 -06:00
```
2019-10-03 11:20:52 -05:00
### Panel size and position
2015-11-02 12:15:40 -06:00
2018-02-21 03:47:14 -06:00
The gridPos property describes the panel size and position in grid coordinates.
2015-11-02 12:15:40 -06:00
2018-02-21 03:47:14 -06:00
- `w` 1-24 (the width of the dashboard is divided into 24 columns)
- `h` In grid height units, each represents 30 pixels.
- `x` The x position, in same unit as `w` .
- `y` The y position, in same unit as `h` .
2015-11-02 12:15:40 -06:00
2018-03-30 09:42:48 -05:00
The grid has a negative gravity that moves panels up if there is empty space above a panel.
2015-11-02 02:21:59 -06:00
### timepicker
2017-02-07 00:48:01 -06:00
```json
2015-11-02 12:15:40 -06:00
"timepicker": {
"collapse": false,
"enable": true,
"notice": false,
"now": true,
"refresh_intervals": [
"5s",
"10s",
"30s",
"1m",
"5m",
"15m",
"30m",
"1h",
"2h",
"1d"
],
"status": "Stable",
"type": "timepicker"
}
```
Usage of the fields is explained below:
2020-09-30 14:45:07 -05:00
| Name | Usage |
| --------------------- | -------------------------------------- |
| **collapse** | whether timepicker is collapsed or not |
| **enable** | whether timepicker is enabled or not |
| **notice** | TODO |
| **now** | TODO |
| **refresh_intervals** | TODO |
| **status** | TODO |
| **type** | TODO |
2015-11-02 02:21:59 -06:00
### templating
2018-03-30 09:47:51 -05:00
The `templating` field contains an array of template variables with their saved values along with some other metadata, for example:
2015-11-02 12:15:40 -06:00
2017-02-07 00:48:01 -06:00
```json
2015-11-02 12:15:40 -06:00
"templating": {
"enable": true,
"list": [
{
"allFormat": "wildcard",
"current": {
"tags": [],
"text": "prod",
"value": "prod"
},
"datasource": null,
"includeAll": true,
"name": "env",
"options": [
{
"selected": false,
"text": "All",
"value": "*"
},
{
"selected": false,
"text": "stage",
"value": "stage"
},
{
"selected": false,
"text": "test",
"value": "test"
}
],
"query": "tag_values(cpu.utilization.average,env)",
"refresh": false,
"type": "query"
},
{
"allFormat": "wildcard",
"current": {
"text": "apache",
"value": "apache"
},
"datasource": null,
"includeAll": false,
"multi": false,
"multiFormat": "glob",
"name": "app",
"options": [
{
"selected": true,
"text": "tomcat",
"value": "tomcat"
},
{
"selected": false,
"text": "cassandra",
"value": "cassandra"
}
],
"query": "tag_values(cpu.utilization.average,app)",
2015-12-01 02:01:44 -06:00
"refresh": false,
2015-11-02 12:15:40 -06:00
"regex": "",
"type": "query"
}
]
}
```
Usage of the above mentioned fields in the templating section is explained below:
2020-09-30 14:45:07 -05:00
| Name | Usage |
| --------------- | ------------------------------------------------------------------------------------------------------- |
| **enable** | whether templating is enabled or not |
| **list** | an array of objects each representing one template variable |
| **allFormat** | format to use while fetching all values from data source, eg: `wildcard` , `glob` , `regex` , `pipe` , etc. |
| **current** | shows current selected variable text/value on the dashboard |
| **data source** | shows data source for the variables |
| **includeAll** | whether all value option is available or not |
| **multi** | whether multiple values can be selected or not from variable value list |
| **multiFormat** | format to use while fetching timeseries from data source |
| **name** | name of variable |
| **options** | array of variable text/value pairs available for selection on dashboard |
| **query** | data source query used to fetch values for a variable |
| **refresh** | TODO |
| **regex** | TODO |
| **type** | type of variable, i.e. `custom` , `query` or `interval` |