Use Grafana to Setup a Dashboard

---

Install Grafana on Ubuntu

wget https://dl.grafana.com/oss/release/grafana_6.0.1_amd64.deb 

sudo apt-get install -y adduser libfontconfig

sudo dpkg -i grafana_6.0.1_amd64.deb 

---

Configure Grafana

Semicolons (the ; char) are the standard way to comment out lines in a .ini file. Change the port number to 9530

vim /etc/grafana/grafana.ini

in grafana ini file, comment starts with #, value comments with ;

# The http port  to use
http_port = 9530

# The full public facing url you use in browser, used for redirects and emails
# If you use reverse proxy and sub path specify full url (with sub path)
root_url = http://localhost:9530

save and restart grafana service

systemctl daemon-reload
systemctl start grafana-server
systemctl status grafana-server
systemctl restart grafana-server

check if grafana works: open browser to http://localhost:9530

more about grafana configuration

---

Set Grafana to HTTPS

1. generate certification file and key save to /etc/ssl/grafana-key.pem, /etc/ssl/grafana-cert.pem

   move to grafana configuration directory

cd /etc/grafana

create a temporary self-signed certificate

openssl genrsa -out selfsigned-grafana.key 2048
openssl req -new -key selfsigned-grafana.key -out selfsigned-grafana.csr
openssl x509 -req -days 365 -in selfsigned-grafana.csr -signkey selfsigned-grafana.key -out selfsigned-grafana.crt

Enter passphrase, and answers some stupid questions like 

* Country Name
* State
* Locality
* Orgnization 
* Unit Name 

change the certification and key file permission

chown grafana:grafana selfsigned-grafana.crt
chown grafana:grafana selfsigned-grafana.key
chmod 400 selfsigned-grafana.crt 
chmod 400 selfsigned-grafana.key

2. change grafana configuration file and restart service

vim /etc/grafana/grafana.ini

[server]
# Protocol (http, https, socket)
protocol = https

# The http port  to use
http_port = 9530

# enable gzip
enable_gzip = true

# https certs & key file
cert_file = "/etc/grafana/selfsigned-grafana.crt"
cert_key = "/etc/grafana/selfsigned-grafana.key"

# set to true if you host Grafana behind HTTPS. default is false.
cookie_secure = true

3. restart the grafana service

systemctl status grafana-server
systemctl restart grafana-server

4. check the grafana logging

vim /var/log/grafana/grafana.log

5. verify https works, open browser and go to https://localhost:9530

---

Install Influxdb

1. install influxdb download and manually install

wget https://dl.influxdata.com/influxdb/releases/influxdb_1.5.0_amd64.deb
sudo dpkg -i influxdb_1.5.0_amd64.deb

add apt repo from the offical website

wget -qO- https://repos.influxdata.com/influxdb.key | sudo apt-key add -
source /etc/lsb-release
echo "deb https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/influxdb.list

install from apt repo

sudo apt-get update && sudo apt-get install influxdb
sudo service influxdb start

everything looks fine

Connected to http://localhost:8086 version 1.7.4
InfluxDB shell version: 1.7.4
Enter an InfluxQL query
> exit

2. Configure Influxdb

The configuration file for InfluxDB is influxdb.conf, it has different location per different OS

• Linux: /etc/influxdb/influxdb.conf

• MacOS: /usr/local/etc/influxdb.conf

vim /etc/influxdb/influxdb.conf

enable https, and set the endpoint to https://localhost:8086

[http]

  [...]

  # Determines whether HTTPS is enabled.
  https-enabled = true

  [...]

  # The TLS or SSL certificate to use when HTTPS is enabled.
  https-certificate = "/etc/influxdb/selfsigned-influxdb.crt"

  # Use a separate private key location.
  https-private-key = "/etc/influxdb/selfsigned-influxdb.key"

generate certification file and key save to /etc/ssl/grafana-key.pem, /etc/ssl/grafana-cert.pem

move to grafana configuration directory

cd /etc/influxdb

create a temporary self-signed certificate

openssl genrsa -out selfsigned-influxdb.key 2048
openssl req -new -key selfsigned-influxdb.key -out selfsigned-influxdb.csr
openssl x509 -req -days 365 -in selfsigned-influxdb.csr -signkey selfsigned-influxdb.key -out selfsigned-influxdb.crt

Enter passphrase, and answers some stupid questions like 

* Country Name: US
* State: CA
* Locality: LA
* Orgnization: Bitconch PTE Ltd.
* Unit Name: Dev-Dashboard-InfluxDB
* Common Name: https://47.103.38.208:8086(server ip)

change the certification and key file permission

chown influxdb:influxdb selfsigned-influxdb.crt
chown influxdb:influxdb selfsigned-influxdb.key
chmod 400 selfsigned-influxdb.crt 
chmod 400 selfsigned-influxdb.key

check the influxdb

sudo systemctl status influxdb

stop the influxdb

sudo systemctl stop influxdb

resetart the infludb

sudo systemctl restart influxdb

connect to https enabled influxdb, since we are using selfsigned certificate, make sure the unsafeSsl is used.

 influx  -ssl -unsafeSsl -host localhost

3. enable authentication

vim /etc/influxdb/influxdb.conf

[http]

# Determines whether user authentication is enabled over HTTP/HTTPS.
  auth-enabled = true

restart the influxdb

sudo systemctl stop influxdb
sudo systemctl restart influxdb
sudo systemctl status influxdb

4. create user for influxdb

influx  -ssl -unsafeSsl -host localhost

create admin, and a user with admin access

CREATE USER admin WITH PASSWORD '<password>' WITH ALL PRIVILEGES

log off and log in again

influx  -ssl -unsafeSsl -host localhost -username 'admin' -password '<password>'

create another user with admin access, and log in using the new user

CREATE USER caesar WITH PASSWORD '<password>' WITH ALL PRIVILEGES
exit
influx  -ssl -unsafeSsl -host localhost -username 'caesar' -password '<password>'

try new user's access, a dummy db is created and dropped.

> SHOW  USERS

> SHOW DATABASES

> CREATE DATABASE dummy1

> SHOW DATABASES

name: databases
name
----
_internal
dummy1

> DROP DATABASE dummy1
> SHOW DATABASES
name: databases
name
----
_internal

> CREATE DATABASE dashboard01

Add InfluxDB Self Signed Certificate

• Ubuntu

• Windows

  Download the /etc/influxdb/selfsigned-influxdb.crt

scp -r -P 22 user@remote_host:/etc/influxdb/selfsigned-influxdb.crt remote_influxdb.crt

Double click the crt file and resave to cer file 

Open and Run MMC

Import the crt file

Update the Grafana Dashboard Configuration

• grafana dash board is defined in testnet-dashboard-stable.json

• set Grafna API Token

  create an orgnization in the dashboard

curl -k -X POST -H "Content-Type: application/json" -d '{"name":"dev-org"}' https://admin:<password>@localhost:9530/api/orgs

{"message":"Organization created","orgId":3}

an orgnization with id 3 is created

curl -k -X POST https://admin:<password>@localhost:9530/api/user/using/3

{"message":"Active organization changed"}

create the API token

curl -k -X POST -H "Content-Type: application/json" -d '{"name":"apikeycurl", "role": "Admin"}' https://admin:zaq12wsx@localhost:9530/api/auth/keys

>{"name":"apikeycurl","key":"eyJrIjoiUWJmTk9hRkx2anVCekVRSWU3UGN3ZkhiM2kxV1I0bnEiLCJuIjoiYXBpa2V5Y3VybCIsImlkIjozfQ=="}
>{"name":"apikeycurl2","key":"eyJrIjoiTVdRaEFiRDF0SThCTjJQTTdOckR2SElndjZ5ZThxdnAiLCJuIjoiYXBpa2V5Y3VybDIiLCJpZCI6M30="}
>{"name":"apikeycurl3","key":"eyJrIjoieG5IbmllOGxJWW9MY3o1dGlmMmNPU0dERzVzYzFKR0EiLCJuIjoiYXBpa2V5Y3VybDMiLCJpZCI6M30="}
>{"name":"dummy1","key":"eyJrIjoid2cyYUlrUnF2OHpIRlNLcW1sMzFYS3MwOEpWUzF6dXgiLCJuIjoiZHVtbXkxIiwiaWQiOjN9"}

set the GRAFANA_API_TOKEN

$ export GRAFANA_API_TOKEN="eyJrIjoiUWJmTk9hRkx2anVCekVRSWU3UGN3ZkhiM2kxV1I0bnEiLCJuIjoiYXBpa2V5Y3VybCIsImlkIjozfQ=="
- set the configuration parameter 

```bash
export DASHBOARD_DB_CONFIG="host=localhost,db=dashboard02,u=caesar,p=<password>"

• run init.sh to initilize metrics database.

  This will set env var DASHBOARD_DB_CONFIG,```

• publish the dashboard

  • install python3 venv

sudo apt-get install python3-venv

* make sure you have the access to avoid ```[email protected]: Permission denied (publickey)``

./publish-metrics-dashboard.sh

Install Rust

$ curl https://sh.rustup.rs -sSf | sh
$ source $HOME/.cargo/env
$ rustup component add rustfmt-preview

$ rustup update

$ sudo apt-get install libssl-dev pkg-config zlib1g-dev llvm clang

$ cargo build --all

Run the test suite:

$ cargo test --all

To emulate all the tests that will run on a Pull Request, run:

$ ./ci/run-local.sh

malformed entry error

if erros like happened:

E: Malformed entry 63 in list file /etc/apt/sources.list (URI parse)
E: The list of sources could not be read.
E: Malformed entry 63 in list file /etc/apt/sources.list (URI parse)
E: The list of sources could not be read.

This error message told us the 63 line of the file /etc/apt/sources.list is invalid, so just commented out the line would be ok. use vim to open /etc/apt/sources.list, and comment out the 63 line, or any other number of line

Solutions for error likes: [email protected]: Permission denied (publickey).

A "Permission denied" error means that the server rejected your connection. on your local machine, you haven't made any SSH keys.

Here's how to fix:

Open git bash (Use the Windows search. To find it, type "git bash") or the Mac Terminal. Pro Tip: You can use any *nix based command prompt (but not the default Windows Command Prompt!) Type cd ~/.ssh. This will take you to the root directory for Git (Likely C:\Users[YOUR-USER-NAME].ssh\ on Windows) Within the .ssh folder, there should be these two files: id_rsa and id_rsa.pub. These are the files that tell your computer how to communicate with GitHub, BitBucket, or any other Git based service. Type ls to see a directory listing. If those two files don't show up, proceed to the next step. NOTE: Your SSH keys must be named id_rsa and id_rsa.pub in order for Git, GitHub, and BitBucket to recognize them by default. To create the SSH keys, type ssh-keygen -t rsa -C "[email protected]". This will create both id_rsa and id_rsa.pub files. Now, go and open id_rsa.pub in your favorite text editor (you can do this via Windows Explorer or the OSX Finder if you like, tpying open . will open the folder). Copy the contents--exactly as it appears, with no extra spaces or lines--of id_rsa.pub and paste it into GitHub and/or BitBucket under the Account Settings > SSH Keys. NOTE: I like to give the SSH key a descriptive name, usually with the name of the workstation I'm on along with the date. Now that you've added your public key to Github and/or BitBucket, try to git push again and see if it works. It should!