Go to file
Kirill Fedoseev d99ca7c6fe Update grafana dashboards 2022-04-21 18:05:30 +02:00
.github/workflows Config JSON schema 2022-03-27 01:47:51 +04:00
config Rework event handlers 2022-04-04 12:21:58 +04:00
contract Rename repo 2022-04-21 15:53:01 +02:00
db Rename repo 2022-04-21 15:53:01 +02:00
entity Add erc_to_native sender 2022-04-13 16:47:57 +04:00
ethclient Add erc_to_native sender 2022-04-13 16:47:57 +04:00
grafana Update grafana dashboards 2022-04-21 18:05:30 +02:00
logging Slack alerts 2021-09-25 21:23:30 +03:00
monitor Rename repo 2022-04-21 15:53:01 +02:00
presenter Rename repo 2022-04-21 15:53:01 +02:00
prometheus Add sender address to alert 2022-04-21 10:39:54 +02:00
repository Rename repo 2022-04-21 15:53:01 +02:00
utils Start alertManager only after bridge logs are fully synced 2021-09-27 01:33:12 +03:00
.dockerignore Bump go version 2021-09-20 01:15:37 +03:00
.env.example Fix prometheus credentials provisioning 2022-04-05 14:35:21 +04:00
.gitignore Add README.md 2022-03-28 12:31:02 +04:00
Dockerfile Rename repo 2022-04-21 15:53:01 +02:00
README.md Rename repo 2022-04-21 15:53:01 +02:00
config.schema.json Rename repo 2022-04-21 15:53:01 +02:00
config.yml Support erc-to-native bridge 2022-04-02 15:49:18 +04:00
docker-compose.dev.yml Add erc_to_native sender 2022-04-13 16:47:57 +04:00
docker-compose.prod.yml Rename repo 2022-04-21 15:53:01 +02:00
go.mod Bump go-ethereum dependency 2022-04-21 16:00:50 +02:00
go.sum Bump go-ethereum dependency 2022-04-21 16:00:50 +02:00
main.go Rename repo 2022-04-21 15:53:01 +02:00

README.md

Tokenbridge monitor

This repo provides a real-time monitoring solution for the AMB/XDAI bridge contracts. It performs a real-time chain indexing for the configured bridged instances, and alerts in case of some important events or outages.

Tech layout

  • Monitor (Golang)
  • PostgreSQL
  • Prometheus
  • Alertmanager (Slack alerts)
  • Grafana (Stats visualization)
  • Traefik for HTTPS routing

Configuration

Monitor configuration is managed through the yml file, processed during the startup (./config.yml). Config schema is described in (./config.schema.json). Config supports env variable interpolation (see INFURA_PROJECT_KEY).

Local start-up

  1. Create env file with INFURA_PROJECT_KEY:
cp .env.example .env
nano .env
  1. Build monitor docker container:
docker-compose -f docker-compose.dev.yml build
  1. In the need of testing Slack alerts in the local deployment, do the following:
# HTTP Basic auth password for prometheus -> alertmanager authentication.
nano ./prometheus/admin_password.txt
# Slack webhook URL for sending alerts. Double check that there is no newline in the end of the file.
printf 'https://hooks.slack.com/services/...' > ./prometheus/slack_api_url.txt
  1. Put bcrypt password hash of ./prometheus/admin_password.txt in ./prometheus/web.yml. Hash can be generated at https://bcrypt-generator.com:
# Set bcrypt hash for admin user
nano ./prometheus/web.yml
  1. Start up:
# Background services
docker-compose -f docker-compose.dev.yml up -d postgres prometheus grafana
# Optionally startup alertmanager
# docker-compose -f docker-compose.dev.yml up -d alertmanager
# Startup monitor
docker-compose -f docker-compose.dev.yml up monitor
  1. Take a look:

Deployment

For final deployment, you will need a VM with a static IP and a DNS domain name attached to that IP. SSL certificates will be managed by a Traefik and Let's Encrypt automatically.

git clone https://github.com/poanetwork/tokenbridge-monitor.git
cd tokenbridge-monitor

cp .env.example .env
nano .env # put valid INFURA_PROJECT_KEY and valid domain names
nano config.yml # modify monitor config if necessary (e.g. disable/enable particular bridges monitoring)

# HTTP Basic auth password for prometheus -> alertmanager authentication.
nano ./prometheus/admin_password.txt
# Slack webhook URL for sending alerts. Double check that there is no newline in the end of the file.
printf 'https://hooks.slack.com/services/...' > ./prometheus/slack_api_url.txt
# Set bcrypt hash for admin user
nano ./prometheus/web.yml

docker-compose -f docker-compose.prod.yml pull
docker-compose -f docker-compose.prod.yml up -d

After a small delay you should be able to access all the services via the provided DNS names through HTTPS. Make sure to change the default admin password in Grafana at the first login.