|
| 1 | +# Telemetry Setup Guide for Bor and Heimdall Nodes |
| 2 | + |
| 3 | +## Overview |
| 4 | + |
| 5 | +This document provides a step-by-step guide to setting up telemetry for monitoring the status of your Bor and Heimdall nodes in real time. |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +## Dashboard Links |
| 10 | + |
| 11 | +We provide dashboards for both **Mainnet** and **Amoy Testnet**: |
| 12 | + |
| 13 | +### **Mainnet** |
| 14 | +- **Bor:** [https://bor-mainnet.vitwit.com/](https://bor-mainnet.vitwit.com/) |
| 15 | +- **Heimdall:** [https://heimdall-mainnet.vitwit.com/](https://heimdall-mainnet.vitwit.com/) |
| 16 | + |
| 17 | +### **Amoy Testnet** |
| 18 | +- **Bor:** [https://bor-amoy.vitwit.com/](https://bor-amoy.vitwit.com/) |
| 19 | +- **Heimdall:** [https://heimdall-amoy.vitwit.com/](https://heimdall-amoy.vitwit.com/) |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## Setting Up Heimdall Telemetry |
| 24 | + |
| 25 | +Follow the steps below to configure telemetry for Heimdall. |
| 26 | + |
| 27 | +### **Step 1: Clone the Repository** |
| 28 | + |
| 29 | +```sh |
| 30 | +git clone https://github.com/vitwit/matic-telemetry.git |
| 31 | +``` |
| 32 | + |
| 33 | +### **Step 2: Configure the Telemetry Directory** |
| 34 | + |
| 35 | +```sh |
| 36 | +cd matic-telemetry |
| 37 | +mkdir -p ~/.telemetry/config |
| 38 | +cp example.config.toml ~/.telemetry/config/config.toml |
| 39 | +``` |
| 40 | + |
| 41 | +### **Step 3: Modify the Configuration File** |
| 42 | + |
| 43 | +Open the configuration file using a text editor: |
| 44 | + |
| 45 | +```sh |
| 46 | +sudo nano ~/.telemetry/config/config.toml |
| 47 | +``` |
| 48 | + |
| 49 | +Modify the following details: |
| 50 | + |
| 51 | +```toml |
| 52 | +[stats_details] |
| 53 | +secret_key = "" |
| 54 | +node = "<node-name>" |
| 55 | +net_stats_ip = "heimdall-amoy.vitwit.com:3000" |
| 56 | +``` |
| 57 | + |
| 58 | +💡 **Note:** The secret key should be set as follows: |
| 59 | +- **Mainnet:** `heimdall_mainnet` |
| 60 | +- **Amoy Testnet:** `amoy-testnet` |
| 61 | + |
| 62 | +### **Step 4: Build and Deploy Telemetry** |
| 63 | + |
| 64 | +```sh |
| 65 | +go mod tidy |
| 66 | +go build -o telemetry |
| 67 | +mv telemetry /usr/bin |
| 68 | +``` |
| 69 | + |
| 70 | +### **Step 5: Create the Telemetry Service** |
| 71 | + |
| 72 | +Create a `telemetry.service` file: |
| 73 | + |
| 74 | +```sh |
| 75 | +echo "[Unit] |
| 76 | +Description=Telemetry |
| 77 | +After=network-online.target |
| 78 | +
|
| 79 | +[Service] |
| 80 | +User=$USER |
| 81 | +ExecStart=$(which telemetry) |
| 82 | +Restart=always |
| 83 | +RestartSec=3 |
| 84 | +LimitNOFILE=4096 |
| 85 | +
|
| 86 | +[Install] |
| 87 | +WantedBy=multi-user.target" | sudo tee "/lib/systemd/system/telemetry.service" |
| 88 | +``` |
| 89 | + |
| 90 | +### **Step 6: Enable and Start the Service** |
| 91 | + |
| 92 | +```sh |
| 93 | +sudo systemctl enable telemetry.service |
| 94 | +sudo systemctl start telemetry.service |
| 95 | +``` |
| 96 | + |
| 97 | +### **Step 7: Verify Logs** |
| 98 | + |
| 99 | +Check the service logs to ensure telemetry is running properly: |
| 100 | + |
| 101 | +```sh |
| 102 | +journalctl -u telemetry -f |
| 103 | +``` |
| 104 | + |
| 105 | +By following these steps, you will successfully configure telemetry for your Heimdall node, ensuring real-time monitoring and improved operational efficiency. |
| 106 | + |
| 107 | +--- |
| 108 | + |
| 109 | +## Setting Up Bor Telemetry |
| 110 | + |
| 111 | +Follow the steps below to configure telemetry for Bor. |
| 112 | + |
| 113 | +### **Step 1: Open the Bor Configuration File** |
| 114 | + |
| 115 | +```sh |
| 116 | +vi /var/lib/bor/config.toml |
| 117 | +``` |
| 118 | + |
| 119 | +### **Step 2: Modify the `ethstats` Flag** |
| 120 | + |
| 121 | +Find the `ethstats` parameter and modify it: |
| 122 | + |
| 123 | +```toml |
| 124 | +ethstats = "<name>:<network>@<url>:3000" |
| 125 | +``` |
| 126 | + |
| 127 | +💡 **Note:** The URL should be entered as follows: |
| 128 | +- **Mainnet: ** `<name>:[email protected]:3000` |
| 129 | +- **Amoy Testnet: ** `<name>:[email protected]:3000` |
| 130 | + |
| 131 | +### **Step 3: Restart Bor** |
| 132 | + |
| 133 | +Restart Bor for the changes to take effect: |
| 134 | + |
| 135 | +```sh |
| 136 | +sudo systemctl restart bor |
| 137 | +``` |
| 138 | + |
| 139 | +You should be able to verify the dashboards once you restart your Bor node. |
| 140 | + |
| 141 | +By following these steps, you will successfully configure telemetry for your Bor node, ensuring real-time monitoring and improved operational efficiency. |
0 commit comments