{"id":512,"date":"2026-06-25T03:11:35","date_gmt":"2026-06-25T03:11:35","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=512"},"modified":"2026-08-22T22:09:23","modified_gmt":"2026-08-22T22:09:23","slug":"setup-prometheus-grafana-vps-monitoring","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/setup-prometheus-grafana-vps-monitoring\/","title":{"rendered":"Prometheus and Grafana on a VPS: A Monitoring Stack That Runs in 512 MB of RAM"},"content":{"rendered":"\n

\u201cPrometheus and Grafana need a dedicated server\u201d is one of the most persistent myths in VPS monitoring. The pair is usually associated with sprawling Kubernetes clusters, but a deliberately sized Prometheus + Grafana setup runs comfortably on a 1 GB VPS and can even fit in 512 MB if you make a few honest trade-offs. This guide walks through installing the stack on a small VPS, the exact settings that keep memory and disk in check, and the handful of alerts that actually matter for a single-node workload.<\/p>\n\n\n\n

What the stack actually costs<\/h2>\n\n\n\n

Before tuning anything, know your baseline. The four components of a minimal stack are Prometheus itself, node_exporter, Grafana, and optionally Alertmanager. On a freshly installed Debian or Ubuntu VPS the resident set sizes look roughly like this:<\/p>\n\n\n\n

Component<\/th>Typical RSS<\/th>Notes<\/th><\/tr><\/thead>
prometheus<\/td>80\u2013150 MB<\/td>Grows with scrape targets and retention<\/td><\/tr>
node_exporter<\/td>15\u201330 MB<\/td>One process per host, very stable<\/td><\/tr>
Grafana<\/td>90\u2013180 MB<\/td>More with many dashboards and plugins<\/td><\/tr>
alertmanager<\/td>20\u201340 MB<\/td>Optional if you alert from Grafana directly<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Total: roughly 250\u2013400 MB for the whole stack. On a 2 GB VPS that is a non-event. On a 512 MB VPS it is survivable, but only if you apply the sizing rules in the next section.<\/p>\n\n\n\n

Install in five commands<\/h2>\n\n\n\n

On Debian 12 \/ Ubuntu 24.04 all three core components are in the official repositories, which means they arrive as properly managed systemd services:<\/p>\n\n\n\n

sudo apt update\nsudo apt install -y prometheus prometheus-node-exporter grafana\nsudo systemctl enable --now prometheus node_exporter grafana-server<\/code><\/pre>\n\n\n\n
Verify each service is listening before moving on: curl -s localhost:9090\/metrics<\/code> should return Prometheus metrics, and Grafana answers on localhost:3000<\/code>. Nothing is exposed to the internet at this point, which is exactly what we want.<\/p>\n\n\n\n
Sizing knobs that matter on a small VPS<\/h2>\n\n\n\n
Four settings separate a lean monitoring stack from one that OOM-kills your web server:<\/p>\n\n\n\n