Skip to main content

Prerequisites

To use Bellydash monitoring, you need:

Technical Requirements​

  • Redbelly Network Node – A running and synchronized node
  • Status Server – The node must have the status server enabled on port 6539
  • Internet access – Monitoring requires a connection to the node
  • Node password – For authorizing operations on the node

Node Configuration​

Before adding a node to monitoring, make sure the status server is enabled. The --statusserver option is part of the node's binary file and allows you to monitor your node's health and status. You can read about it in the official Redbelly Developer Portal.

Step 1: Create a backup​

Always create a backup before modifying configuration:

sudo cp /etc/systemd/system/redbelly.service /etc/systemd/system/redbelly.service.backup

Step 2: Edit the service file​

Open the systemd configuration file:

Option A: Using nano (easier)

sudo nano /etc/systemd/system/redbelly.service

Option B: Using vi/vim (advanced)

sudo vi /etc/systemd/system/redbelly.service

Step 3: Add monitoring parameters​

Find the line starting with ExecStart=. It should look similar to:

ExecStart=/opt/redbelly/redbelly [other-options] --mainnet

IMPORTANT: Add the following parameters BEFORE --mainnet:

ExecStart=/opt/redbelly/redbelly [other-options] --statusserver.addr=0.0.0.0 --statusserver.port=6539 --prometheus.addr=127.0.0.1 --mainnet

Before/After example:

Before:

ExecStart=/opt/redbelly/redbelly [other-options] --mainnet

After:

ExecStart=/opt/redbelly/redbelly [other-options] --statusserver.addr=0.0.0.0 --statusserver.port=6539 --prometheus.addr=127.0.0.1 --mainnet

Parameter explanation:

  • --statusserver.addr=0.0.0.0 - Allows external connections
  • --statusserver.port=6539 - Port for status server
  • --prometheus.addr=127.0.0.1 - Prometheus metrics only locally

Step 4: Save the file and restart the service​

  • In nano: Press Ctrl+X, then Y, then Enter
  • In vi/vim: Press Esc, type :wq, press Enter

Then perform a restart:

# Reload systemd configuration
sudo systemctl daemon-reload

# Restart the service
sudo systemctl start redbelly.service

# Check status
sudo systemctl status redbelly.service

Check if the service is running:

sudo systemctl is-active redbelly.service

Should return: active

Step 5: Configure firewall​

Ubuntu/Debian (ufw):

# Check firewall status
sudo ufw status

# Open port 6539
sudo ufw allow 6539/tcp

# Check if the rule was added
sudo ufw status numbered

OR restrict access to a specific IP:

sudo ufw allow from [Your home IP] to any port 6539 proto tcp
sudo ufw allow from [Our site IP] to any port 6539 proto tcp

Step 6: Verify configuration​

Local test:

# Check if status server responds
curl http://127.0.0.1:6539/status

# Check Prometheus metrics
curl http://127.0.0.1:6539/metrics

The result should appear as JSON (for /status) or in Prometheus format (for /metrics).

External test:

Make sure port 6539 is open in the firewall, then open in a browser:

  • http://SERVER_IP:6539/status or
  • http://SERVER_IP:6539/metrics

Registration and Access​

  • Monitoring works without registration – just add a node using its IP address and password
  • The panel is accessible from any device (computer, phone, tablet)
  • Telegram alerts require connecting to a bot (instructions in the Alerts section)