b6e46c9eb8
A simple version control system for dashboards. Closes #1504. Goals 1. To create a new dashboard version every time a dashboard is saved. 2. To allow users to view all versions of a given dashboard. 3. To allow users to rollback to a previous version of a dashboard. 4. To allow users to compare two versions of a dashboard. Usage Navigate to a dashboard, and click the settings cog. From there, click the "Changelog" button to be brought to the Changelog view. In this view, a table containing each version of a dashboard can be seen. Each entry in the table represents a dashboard version. A selectable checkbox, the version number, date created, name of the user who created that version, and commit message is shown in the table, along with a button that allows a user to restore to a previous version of that dashboard. If a user wants to restore to a previous version of their dashboard, they can do so by clicking the previously mentioned button. If a user wants to compare two different versions of a dashboard, they can do so by clicking the checkbox of two different dashboard versions, then clicking the "Compare versions" button located below the dashboard. From there, the user is brought to a view showing a summary of the dashboard differences. Each summarized change contains a link that can be clicked to take the user a JSON diff highlighting the changes line by line. Overview of Changes Backend Changes - A `dashboard_version` table was created to store each dashboard version, along with a dashboard version model and structs to represent the queries and commands necessary for the dashboard version API methods. - API endpoints were created to support working with dashboard versions. - Methods were added to create, update, read, and destroy dashboard versions in the database. - Logic was added to compute the diff between two versions, and display it to the user. - The dashboard migration logic was updated to save a "Version 1" of each existing dashboard in the database. Frontend Changes - New views - Methods to pull JSON and HTML from endpoints New API Endpoints Each endpoint requires the authorization header to be sent in the format, ``` Authorization: Bearer <jwt> ``` where `<jwt>` is a JSON web token obtained from the Grafana admin panel. `GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"` Get all dashboard versions for the given dashboard ID. Accepts three URL parameters: - `orderBy` String to order the results by. Possible values are `version`, `created`, `created_by`, `message`. Default is `versions`. Ordering is always in descending order. - `limit` Maximum number of results to return - `start` Position in results to start from `GET "/api/dashboards/db/:dashboardId/versions/:id"` Get an individual dashboard version by ID, for the given dashboard ID. `POST "/api/dashboards/db/:dashboardId/restore"` Restore to the given dashboard version. Post body is of content-type `application/json`, and must contain. ```json { "dashboardId": <int>, "version": <int> } ``` `GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"` Compare two dashboard versions by ID for the given dashboard ID, returning a JSON delta formatted representation of the diff. The URL format follows what GitHub does. For example, visiting [/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33) will return the diff between versions 22 and 33 for the dashboard ID 18. Dependencies Added - The Go package [gojsondiff](https://github.com/yudai/gojsondiff) was added and vendored. |
||
|---|---|---|
| .github | ||
| .hooks | ||
| conf | ||
| docker | ||
| docs | ||
| emails | ||
| examples | ||
| packaging | ||
| pkg | ||
| public | ||
| scripts | ||
| tasks | ||
| tests | ||
| vendor | ||
| .bowerrc | ||
| .bra.toml | ||
| .editorconfig | ||
| .floo | ||
| .flooignore | ||
| .gitignore | ||
| .jscs.json | ||
| .jsfmtrc | ||
| .jshintrc | ||
| appveyor.yml | ||
| bower.json | ||
| build.go | ||
| CHANGELOG.md | ||
| circle.yml | ||
| Gruntfile.js | ||
| karma.conf.js | ||
| latest.json | ||
| LICENSE.md | ||
| Makefile | ||
| NOTICE.md | ||
| package.json | ||
| README.md | ||
| ROADMAP.md | ||
| tsconfig.json | ||
| tslint.json | ||
| yarn.lock | ||
Grafana 
Website | Twitter | Community & Forum
Grafana is an open source, feature rich metrics dashboard and graph editor for Graphite, Elasticsearch, OpenTSDB, Prometheus and InfluxDB.
- Install instructions
- What's New in Grafana 2.0
- What's New in Grafana 2.1
- What's New in Grafana 2.5
- What's New in Grafana 3.0
- What's New in Grafana 4.0
- What's New in Grafana 4.1
- What's New in Grafana 4.2
- What's New in Grafana 4.3
Features
Graphing
- Fast rendering, even over large timespans
- Click and drag to zoom
- Multiple Y-axis, logarithmic scales
- Bars, Lines, Points
- Smart Y-axis formatting
- Series toggles & color selector
- Legend values, and formatting options
- Grid thresholds, axis labels
- Annotations
- Any panel can be rendered to PNG (server side using phantomjs)
Dashboards
- Create, edit, save & search dashboards
- Change column spans and row heights
- Drag and drop panels to rearrange
- Templating
- Scripted dashboards
- Dashboard playlists
- Time range controls
- Share snapshots publicly
InfluxDB
- Use InfluxDB as a metric data source, annotation source
- Query editor with field and tag typeahead, easy group by and function selection
Graphite
- Graphite target expression parser
- Feature rich query composer
- Quickly add and edit functions & parameters
- Templated queries
- See it in action
Elasticsearch, Prometheus & OpenTSDB
- Feature rich query editor UI
Alerting
- Define alert rules using graphs & query conditions
- Schedule & evalute alert rules, send notifications to Slack, Hipchat, Email, PagerDuty, etc.
Requirements
There are no dependencies except an external time series data store. For dashboards and user accounts Grafana can use an embedded database (sqlite3) or you can use an external SQL data base like MySQL or Postgres.
Installation
Head to grafana.org and download the latest release.
If you have any problems please read the troubleshooting guide.
Documentation & Support
Be sure to read the getting started guide and the other feature guides.
Run from master
If you want to build a package yourself, or contribute. Here is a guide for how to do that. You can always find the latest master builds here
Dependencies
- Go 1.8.1
- NodeJS LTS
Get Code
go get github.com/grafana/grafana
Since imports of dependencies use the absolute path github.com/grafana/grafana within the $GOPATH,
you will need to put your version of the code in $GOPATH/src/github.com/grafana/grafana to be able
to develop and build grafana on a cloned repository. To do so, you can clone your forked repository
directly to $GOPATH/src/github.com/grafana or you can create a symbolic link from your version
of the code to $GOPATH/src/github.com/grafana/grafana. The last options makes it possible to change
easily the grafana repository you want to build.
go get github.com/*your_account*/grafana
mkdir $GOPATH/src/github.com/grafana
ln -s $GOPATH/src/github.com/*your_account*/grafana $GOPATH/src/github.com/grafana/grafana
Building the backend
cd $GOPATH/src/github.com/grafana/grafana
go run build.go setup
go run build.go build
Building frontend assets
To build less to css for the frontend you will need a recent version of node (v6+), npm (v2.5.0) and grunt (v0.4.5). Run the following:
npm install -g yarn
yarn install --pure-lockfile
npm run build
To build the frontend assets only on changes:
sudo npm install -g grunt-cli # to do only once to install grunt command line interface
grunt watch
Recompile backend on source change
To rebuild on source change.
go get github.com/Unknwon/bra
bra run
Running
./bin/grafana-server
Open grafana in your browser (default: http://localhost:3000) and login with admin user (default: user/pass = admin/admin).
Dev config
Create a custom.ini in the conf directory to override default configuration options. You only need to add the options you want to override. Config files are applied in the order of:
- grafana.ini
- dev.ini (if found)
- custom.ini
Create a pull request
Before or after you create a pull request, sign the contributor license agreement.
Contribute
If you have any idea for an improvement or found a bug do not hesitate to open an issue. And if you have time clone this repo and submit a pull request and help me make Grafana the kickass metrics & devops dashboard we all dream about!
License
Grafana is distributed under Apache 2.0 License. Work in progress Grafana 2.0 (with included Grafana backend)