280 Commits (233cd7af4a8924b6841c92a1e9a43f4daa3181b5)

Author	SHA1	Message	Date
Daniel Lee	233cd7af4a	WIP: add user group search	8 years ago
Torkel Ödegaard	ef1dfed0d8	dasboard_history: big refactoring of how the compare api looked, now a POST with a model for new & base version, refactored a simplified UI code as well, this was done to lay foundation to make it possible to do diff against current in browser unsaved version	8 years ago
Torkel Ödegaard	689e366f59	refactoring: updated api url routes so they do not conflict with slug route	8 years ago
Torkel Ödegaard	c87418d060	refactoring: Dashboard history restore operation is now reusing existing ... operations instead of duplicating a bunch of get & save logic.	8 years ago
sanchitraizada	77c046aac6	Implement review feedback	8 years ago
Torkel Ödegaard	0d865a83bc	fix: fixed test data fake metric query, fixes #8474	8 years ago
Torkel Ödegaard	0d39852ef4	fix: fixed test data fake metric query, fixes #8474	8 years ago
Ben Tranter	b6e46c9eb8	History and Version Control for Dashboard Updates ... 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.	8 years ago
Torkel Ödegaard	0156a94a49	annotations: you can now read annoations via manually created annoation query	8 years ago
Alexander Zobnin	d553498a33	graph(add annotation): initial backend implementation #1286	8 years ago
Torkel Ödegaard	bd4f073425	mysql: minor update	8 years ago
Daniel Lee	193d468ed3	admin: adds paging to global user list ... Currently there is a limit of 1000 users in the global user list. This change introduces paging so that an admin can see all users and not just the first 1000. Adds a new route to the api - /api/users/search that returns a list of users and a total count. It takes two parameters perpage and page that enable paging. Fixes #7469	8 years ago
huydx	143cbe921f	(feat) support datasource delete by name api	9 years ago
Daniel Lee	1294b203e6	admin: adds paging to global user list ... Currently there is a limit of 1000 users in the global user list. This change introduces paging so that an admin can see all users and not just the first 1000. Adds a new route to the api - /api/users/search that returns a list of users and a total count. It takes two parameters perpage and page that enable paging. Fixes #7469	9 years ago
Pavlos Daoglou	3e741315b4	[3743] Adds support for user search based on login or email (#7334) ... * [3743] Adds support for user search based on login or email * Use query parameter instead * Use macaron Query() instead	9 years ago
Torkel Ödegaard	b8f559aecb	feat(plugins): made notifiers more pluggable and easier to support many of them, new ones can now be added without modifying any existing file, #7162	9 years ago
Torkel Ödegaard	fad07f0d15	refactor(http): refactoring http server	9 years ago
bergquist	a2257ec3d0	tech(alerting): renames pause all method	9 years ago
bergquist	ecdf1888c4	feat(alerting): removes pause per datasource	9 years ago
bergquist	fb6aa0e026	feat(api): adds endpoint for mass pausing alerts ... ref #6589	9 years ago
bergquist	8ee85626f2	fix(api): return correct json info after updating datasource ... closes #6869	9 years ago
Torkel Ödegaard	e3564d12a1	fix(404): fixed 404 page	9 years ago
Torkel Ödegaard	fb57bf77da	ux(getting started): progress on getting started panel and persited help flag states, #6466	9 years ago
bergquist	b2d5b920f5	feat(alerting): allow editor to modify notifications ... closes #6314	9 years ago
Torkel Ödegaard	4c26c55fea	fix(api): minor change to how pause alert was done	9 years ago
Torkel Ödegaard	c9d7eb0a7a	feat(alerting): added clear history button to alert state history view, #6244	9 years ago
bergquist	c6cf7647ff	feat(alerting): pausing alerts requires alert id	9 years ago
bergquist	804797245d	feat(alerting): make it possible to pause from alert tab	9 years ago
bergquist	264590a9c2	feat(alerting): add paused api endpoint	9 years ago
Torkel Ödegaard	7c339f0794	feat(alerting): show alertin state in panel header, closes #6136	9 years ago
Torkel Ödegaard	3ecd96e682	feat(testdata): lots of work on new test data data source and scenarios	9 years ago
Dan Cech	2c3dd84ebb	allow non-admin users to view plugin readme	9 years ago
Torkel Ödegaard	936146768f	fix(snapshots): fixed issue with viewing embedded/solo/png panel from snapshot without login, fixes #3769	9 years ago
Torkel Ödegaard	d60bd77658	feat(annotations): added support to show grafana stored annotations in graphs, #5982	9 years ago
bergquist	d11bc57c37	feat(notifications): make it possible to send test alert notifications ... closes #5847	9 years ago
bergquist	11a4ff0f8a	feat(alerting): add basic UI for history in alert tab ... ref #5850	9 years ago
bergquist	650a87dc05	feat(alerting): add alert history api endpoint ... ref #5850	9 years ago
chrismartin0077	0050707134	feat(api) HEAD response, fixes #3854	9 years ago
bergquist	0cbedb4473	chore(api): remove commented endpoints	9 years ago
Torkel Ödegaard	7eb2d2cf47	feat(alerting): working on state management	9 years ago
Torkel Ödegaard	9e91aacd34	feat(alerting): progress on testing alerts	9 years ago
Torkel Ödegaard	fb636344a6	feat(alerting): began work on testing alert rule from UI without having to save it	9 years ago
Torkel Ödegaard	f13b869aa4	feat(alerting): work on alerting	9 years ago
Torkel Ödegaard	624cd6fc0a	feat(alerting): cleanup, removed alert changes table and code	9 years ago
Torkel Ödegaard	d44325affd	feat(apps): progress on app dashboard imports	9 years ago
bergquist	a18506e2e4	feat(alerting): changing notifications should require org admin	9 years ago
bergquist	0c5da9155f	feat(alerting): only expose DTO info when requesting all notifications	9 years ago
Torkel Ödegaard	9f9fca1e76	feat(datasource): added suggest urls for each data source, #4577	9 years ago
bergquist	b035074613	tech(alerting): disable update state api	9 years ago
bergquist	b907ce341c	feat(alerting): enables deletes for alert notifications	9 years ago