|
|
1 year ago | |
|---|---|---|
| .. | ||
| grafana-provisioning | 1 year ago | |
| .gitignore | 6 years ago | |
| README.md | 6 years ago | |
| adjust-dashboard-for-channel.py | 5 years ago | |
| enable.sh | 6 years ago | |
| grafana.ini | 6 years ago | |
| influxdb.conf | 6 years ago | |
| start.sh | 5 years ago | |
| status.sh | 6 years ago | |
| stop.sh | 6 years ago | |
| test.sh | 6 years ago | |
This directory contains scripts to manage a local instance of InfluxDB OSS and Grafana
Start the local metric services:
$ ./start.sh
Metrics are enabled on a per-shell basis which means you must source the
following scripts in each shell in which you start an application you wish to
collect metrics from. For example, if running a Solana validator you must run
source ./enable.sh before starting the node:
$ source ./enable.sh
Once metrics have been started and you have an application running you can view the metrics at:
http://localhost:3000/dashboards
To test that things are working correctly you can send a test airdrop data point and then check the metrics dashboard:
$ ./test.sh
Stop metric services:
$ ./stop.sh
You may find it useful to install the InfluxDB client for adhoc metrics collection/viewing
sudo apt-get install influxdb-clientbrew install influxdbSimple example of pulling all airdrop measurements out of the testnet database:
$ influx -database testnet -username read -password read -execute 'SELECT * FROM "faucet-airdrop"'
Reference: https://docs.influxdata.com/influxdb/v1.5/query_language/
To monitor activity, run one of:
$ docker logs -f influxdb
$ docker logs -f grafana