DPTCloud
Back to articles
Technology Insight

Building a Free VPS Monitoring & Alert System with Prometheus, Grafana, and Telegram Bot

May 16, 2026

Introduction: The Imperative of Proactive Server Monitoring

In today's digital landscape, the health and performance of your Virtual Private Server (VPS) are non-negotiable for maintaining online presence, application reliability, and user satisfaction. Downtime, performance degradation, or security breaches can have immediate financial and reputational consequences. While enterprise monitoring solutions exist, they often come with significant licensing costs and complexity. This guide presents a sophisticated yet entirely free alternative: building a comprehensive monitoring and alerting system using the open-source power trio of Prometheus for metrics collection, Grafana for visualization, and a Telegram Bot for real-time alerts. This stack provides enterprise-grade capabilities without the enterprise price tag, offering full visibility and control over your infrastructure.

Architectural Overview: How the Components Interact

The system's architecture follows a modular, scalable design. Prometheus acts as the central time-series database and metrics engine. It operates on a pull model, periodically scraping metrics from configured targets. On the VPS itself, we deploy exporters—lightweight processes that expose system metrics in a format Prometheus understands. The Node Exporter is crucial, providing detailed data on CPU, memory, disk, network, and other host-level statistics.

Grafana connects to Prometheus as a data source. It is the visualization layer where you build dashboards to transform raw metrics into intuitive graphs, gauges, and tables. Grafana's strength lies in its flexibility and rich ecosystem of community-built dashboards.

The alerting pipeline involves two stages. First, Prometheus evaluates alerting rules defined in its configuration. When a rule condition is met (e.g., memory usage > 90% for 5 minutes), it fires an alert. This alert is then sent to the Alertmanager, another component of the Prometheus ecosystem. Alertmanager handles deduplication, grouping, and routing of alerts to various receivers. We configure it to send alerts via a webhook to a custom Telegram Bot, which delivers instant notifications directly to your mobile device or team chat. This creates a closed-loop system from detection to notification.

Step-by-Step Implementation Guide

1. Prerequisites and Initial Setup

Begin with a freshly provisioned VPS running a common Linux distribution like Ubuntu 22.04 LTS or Debian 11. Ensure you have sudo privileges. Update your system packages: sudo apt update && sudo apt upgrade -y. This guide assumes basic familiarity with the command line, Docker, and fundamental networking concepts.

2. Installing and Configuring Prometheus

We will use Docker for ease of deployment and management. First, create a directory structure to persist configuration and data:

sudo mkdir -p /opt/monitoring/prometheus/data
sudo chmod 777 /opt/monitoring/prometheus/data

Create the core Prometheus configuration file at /opt/monitoring/prometheus/prometheus.yml. This file defines what to scrape and how to evaluate alerts.

global:
  scrape_interval: 15s
  evaluation_interval: 15s
alerting:
  alertmanagers:
    - static_configs:
        - targets: ['alertmanager:9093']
rule_files:
  - '/etc/prometheus/alert_rules.yml'
scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']
  - job_name: 'node_exporter'
    static_configs:
      - targets: ['node_exporter:9100']

Next, define alerting rules in /opt/monitoring/prometheus/alert_rules.yml. These are the conditions that will trigger notifications.

groups:
- name: host_alerts
  rules:
  - alert: HighMemoryUsage
    expr: (node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100 > 85
    for: 5m
    labels:
      severity: warning
    annotations:
      summary: "High memory usage on {{ $labels.instance }}"
      description: "Memory usage is at {{ $value | printf "%.2f" }}%."
  - alert: InstanceDown
    expr: up == 0
    for: 1m
    labels:
      severity: critical
    annotations:
      summary: "Instance {{ $labels.instance }} down"
      description: "{{ $labels.instance }} has been down for more than 1 minute."

Launch Prometheus using Docker:

docker run -d \
  --name=prometheus \
  --network=monitoring \
  -p 9090:9090 \
  -v /opt/monitoring/prometheus/prometheus.yml:/etc/prometheus/prometheus.yml \
  -v /opt/monitoring/prometheus/alert_rules.yml:/etc/prometheus/alert_rules.yml \
  -v /opt/monitoring/prometheus/data:/prometheus \
  prom/prometheus:latest

3. Deploying the Node Exporter

The Node Exporter exposes host metrics. Run it as a container:

docker run -d \
  --name=node_exporter \
  --network=monitoring \
  --pid="host" \
  -p 9100:9100 \
  -v "/:/host:ro,rslave" \
  quay.io/prometheus/node-exporter:latest \
  --path.rootfs=/host

4. Setting Up Alertmanager with Telegram Integration

First, create a Telegram Bot via BotFather and obtain its API token. Create a group chat, add the bot, and retrieve the chat ID (you can use the getUpdates API method).

Create the Alertmanager configuration at /opt/monitoring/alertmanager/alertmanager.yml:

global:
  smtp_smarthost: 'localhost:25'
  smtp_from: '[email protected]'
route:
  group_by: ['alertname', 'cluster']
  group_wait: 10s
  group_interval: 10s
  repeat_interval: 1h
  receiver: 'telegram'
receivers:
- name: 'telegram'
  webhook_configs:
  - url: 'http://telegram-bot:8080/alert'
    send_resolved: true

You will need a simple web service to bridge Alertmanager webhooks to the Telegram Bot API. A minimal Python script using Flask can serve this purpose. Create /opt/monitoring/telegram-bot/bot.py:

from flask import Flask, request
import requests
app = Flask(__name__)
TELEGRAM_TOKEN = 'YOUR_BOT_TOKEN'
CHAT_ID = 'YOUR_CHAT_ID'
TELEGRAM_API_URL = f'https://api.telegram.org/bot{TELEGRAM_TOKEN}/sendMessage'
@app.route('/alert', methods=['POST'])
def alert():
    data = request.get_json()
    for alert in data.get('alerts', []):
        status = alert.get('status')
        labels = alert.get('labels', {})
        annotations = alert.get('annotations', {})
        summary = annotations.get('summary', 'No summary')
        description = annotations.get('description', 'No description')
        severity = labels.get('severity', 'info')
        emoji = '🔴' if status == 'firing' else '🟢'
        message = f"{emoji} *{severity.upper()}*: {summary}\n\n{description}"
        payload = {'chat_id': CHAT_ID, 'text': message, 'parse_mode': 'Markdown'}
        requests.post(TELEGRAM_API_URL, json=payload)
    return 'OK', 200
if __name__ == '__main__':
    app.run(host='0.0.0.0', port=8080)

Run this bot and Alertmanager using Docker Compose for better orchestration, or as individual containers on the same network.

5. Installing and Configuring Grafana

Deploy Grafana, connecting it to your Prometheus data source:

docker run -d \
  --name=grafana \
  --network=monitoring \
  -p 3000:3000 \
  -v /opt/monitoring/grafana/data:/var/lib/grafana \
  grafana/grafana-oss:latest

Access Grafana at http://your-vps-ip:3000 (default login: admin/admin). Add Prometheus as a data source (URL: http://prometheus:9090). Then, import a pre-built dashboard for the Node Exporter. The dashboard ID 1860 from the Grafana community is an excellent starting point for comprehensive host monitoring.

Advanced Configuration and Best Practices

Securing Your Monitoring Stack

Exposing Prometheus (port 9090) and Grafana (port 3000) directly to the internet is a security risk. Implement the following measures:

  • Use a reverse proxy (like Nginx or Caddy) with HTTPS termination and authentication.
  • Employ firewall rules (UFW or iptables) to restrict access to specific source IPs.
  • Change default passwords, especially for Grafana.
  • Consider using Docker secrets or environment files for sensitive data like the Telegram bot token, rather than hardcoding them.

Optimizing Performance and Resource Usage

This stack is lightweight, but optimization ensures it doesn't monitor itself into a resource crisis.

  • Scrape Intervals: Adjust the scrape_interval in prometheus.yml. For most VPS purposes, 15-30 seconds is sufficient. More frequent scraping increases storage and load.
  • Data Retention: Prometheus data defaults to 15 days. Modify the --storage.tsdb.retention.time flag in the Docker run command if you need longer retention. Be mindful of disk space.
  • Alert Grouping: Fine-tune Alertmanager's group_wait, group_interval, and repeat_interval to avoid alert fatigue while ensuring timely notifications.

Scaling and Monitoring Multiple Servers

The true power of this architecture shines when monitoring multiple VPS instances. Simply add new job_name entries to the prometheus.yml scrape_configs, pointing to the IP and port (9100) of the Node Exporter on each additional server. You can use static configurations for a handful of servers or explore service discovery mechanisms (like DNS-based or file-based) for dynamic environments. All metrics will be centralized in your single Prometheus instance, and dashboards in Grafana can aggregate data across all hosts.

Conclusion: Empowerment Through Open Source

Building your own monitoring and alerting system with Prometheus, Grafana, and a Telegram bot is more than a cost-saving exercise; it is an exercise in infrastructure empowerment. You gain deep, actionable insights into your server's performance, configure alerts tailored to your specific operational thresholds, and receive notifications through a ubiquitous communication platform. This solution demystifies infrastructure monitoring, proving that enterprise-grade observability is accessible, adaptable, and firmly within the reach of any developer or system administrator willing to invest time in open-source technologies. By implementing this stack, you transition from reactive firefighting to proactive management, ensuring the stability and performance that your services and users deserve.