dc9ec7dc91
* Modify backend to allow expiration of API Keys * Add middleware test for expired api keys * Modify frontend to enable expiration of API Keys * Fix frontend tests * Fix migration and add index for `expires` field * Add api key tests for database access * Substitude time.Now() by a mock for test usage * Front-end modifications * Change input label to `Time to live` * Change input behavior to comply with the other similar * Add tooltip * Modify AddApiKey api call response Expiration should be *time.Time instead of string * Present expiration date in the selected timezone * Use kbn for transforming intervals to seconds * Use `assert` library for tests * Frontend fixes Add checks for empty/undefined/null values * Change expires column from datetime to integer * Restrict api key duration input It should be interval not number * AddApiKey must complain if SecondsToLive is negative * Declare ErrInvalidApiKeyExpiration * Move configuration to auth section * Update docs * Eliminate alias for models in modified files * Omit expiration from api response if empty * Eliminate Goconvey from test file * Fix test Do not sleep, use mocked timeNow() instead * Remove index for expires from api_key table The index should be anyway on both org_id and expires fields. However this commit eliminates completely the index for now since not many rows are expected to be in this table. * Use getTimeZone function * Minor change in api key listing The frontend should display a message instead of empty string if the key does not expire. |
||
---|---|---|
.circleci | ||
.github | ||
conf | ||
devenv | ||
docs | ||
emails | ||
packages | ||
packaging | ||
pkg | ||
public | ||
scripts | ||
style_guides | ||
tools/phantomjs | ||
vendor | ||
.babelrc | ||
.bra.toml | ||
.browserslistrc | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
.prettierignore | ||
build.go | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
Gruntfile.js | ||
ISSUE_TRIAGE.md | ||
jest.config.e2e.js | ||
jest.config.js | ||
latest.json | ||
LICENSE | ||
Makefile | ||
NOTICE.md | ||
package.json | ||
PLUGIN_DEV.md | ||
README.md | ||
ROADMAP.md | ||
SECURITY.md | ||
SUPPORT.md | ||
tsconfig.json | ||
tslint.json | ||
UPGRADING_DEPENDENCIES.md | ||
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.
Installation
Head to docs.grafana.org for documentation or download to get the latest release.
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 (Latest Stable)
- Node.js LTS
- yarn [
npm install -g yarn
]
- yarn [
Get the project
The project located in the go-path will be your working directory.
go get github.com/grafana/grafana
cd $GOPATH/src/github.com/grafana/grafana
Run and rebuild on source change
Backend
To run the backend and rebuild on source change:
make run
Frontend
Rebuild on file change, and serve them by Grafana's webserver (http://localhost:3000):
yarn start
Build the assets, rebuild on file change with Hot Module Replacement (HMR), and serve them by webpack-dev-server (http://localhost:3333):
yarn start:hot
# OR set a theme
env GRAFANA_THEME=light yarn start:hot
Note: HMR for Angular is not supported. If you edit files in the Angular part of the app, the whole page will reload.
Run tests and rebuild on source change:
yarn jest
Open grafana in your browser (default: e.g. http://localhost:3000
) and login with admin user (default: user/pass = admin/admin
).
Building
The backend
go run build.go setup
go run build.go build
Frontend assets
For this you need Node.js (LTS version).
yarn install --pure-lockfile
Building a Docker image
There are two different ways to build a Grafana docker image. If your machine is setup for Grafana development and you run linux/amd64 you can build just the image. Otherwise, there is the option to build Grafana completely within Docker.
Run the image you have built using: docker run --rm -p 3000:3000 grafana/grafana:dev
Building on linux/amd64 (fast)
- Build the frontend
go run build.go build-frontend
- Build the docker image
make build-docker-dev
The resulting image will be tagged as grafana/grafana:dev
Building anywhere (slower)
Choose this option to build on platforms other than linux/amd64 and/or not have to setup the Grafana development environment.
make build-docker-full
ordocker build -t grafana/grafana:dev .
The resulting image will be tagged as grafana/grafana:dev
Notice: If you are using Docker for MacOS, be sure to set the memory limit to be larger than 2 GiB (at docker -> Preferences -> Advanced), otherwise grunt build
may fail.
Development
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
- custom.ini
In your custom.ini uncomment (remove the leading ;
) sign. And set app_mode = development
.
Running tests
Frontend
Execute all frontend tests
yarn test
Writing & watching frontend tests
- Start watcher:
yarn jest
- Jest will run all test files that end with the name ".test.ts"
Backend
# Run Golang tests using sqlite3 as database (default)
go test ./pkg/...
# Run Golang tests using mysql as database - convenient to use /docker/blocks/mysql_tests
GRAFANA_TEST_DB=mysql go test ./pkg/...
# Run Golang tests using postgres as database - convenient to use /docker/blocks/postgres_tests
GRAFANA_TEST_DB=postgres go test ./pkg/...
End-to-end
Execute all end-to-end tests
yarn e2e-tests
Execute all end-to-end tests using using a specific url
ENV BASE_URL=http://localhost:3333 yarn e2e-tests
Debugging all end-to-end tests (BROWSER=1 will start the browser and SLOWMO=1 will delay each puppeteer operation by 100ms)
ENV BROWSER=1 SLOWMO=1 yarn e2e-tests
Datasource and dashboard provisioning
Here you can find helpful scripts and docker-compose setup that will populate your dev environment for quicker testing end experimenting.
Contribute
If you have any ideas for improvement or have found a bug, do not hesitate to open an issue. And if you have time, clone this repo and submit a pull request to help me make Grafana the kickass metrics & devops dashboard we all dream about!
Read the contributing guide then check the beginner friendly
label to find issues that are easy and that we would like help with.
Plugin development
Checkout the Plugin Development Guide and checkout the PLUGIN_DEV.md file for changes in Grafana that relate to plugin development.
License
Grafana is distributed under Apache 2.0 License.