🤖 Bellydash Telegram Bot Documentation
Guide to Notifications and Alerts
Introduction
The Bellydash Telegram bot provides real‑time notifications about the status and performance of your Redbelly Network node. Its purpose is to ensure that you are immediately informed about any issues, anomalies, or important state changes.
This document explains:
- why you receive each type of notification
- what each alert means
- how you should react
- how the bot decides when to send a message
- technical details of the alerting logic and thresholds
ℹ️ Info
The goal is to give node operators full clarity and confidence in how the monitoring and alerting system behaves.
How does the bot work?
The Bellydash bot continuously monitors your node 24/7, collecting fresh metrics every 15 seconds. These metrics include:
- node availability
- synchronization status
- block production
- peer count
- resource usage (CPU, RAM, disk)
- network responsiveness
- internal health indicators
When the system detects a status change, anomaly, or problem, it immediately triggers an alert and sends it to your Telegram chat.
This ensures:
- instant awareness of issues
- minimal downtime
- fast reaction time
- full transparency of node behavior
The bot is designed to be both proactive (detecting problems early) and non‑intrusive (avoiding spam by grouping or suppressing redundant alerts when appropriate).
💡 Tip
All notifications are sent automatically. You don't need to do anything, the bot works in the background and only informs you when something requires attention.
Notification Types
- Welcome Message - Sent once after activating alerts
- OFFLINE Alert - Node stopped responding
- ONLINE Alert - Node returned to operation
- High Latency Alert - Node responds too slowly
- Restart Alert - Node process restart detected
- Weekly Report - Week summary
- Synchronization Alerts - Synchronization status change