Analytics & Monitoring1 GB RAM (Pro recommended)· Port 9090

Deploy Prometheus Time-Series Monitoring with Docker Compose

Cloud-native time-series database and alerting toolkit for scraping container and application metrics.

1. Production docker-compose.yml Configuration

Copy this stack definition or deploy directly from your Vexlo Cloud console with automatic Let's Encrypt TLS and persistent volume mounts.

docker-compose.yml
yaml
services:
  prometheus:
    image: prom/prometheus:latest
    restart: unless-stopped
    ports:
      - "9090:9090"
    environment:
      - PROMETHEUS_RETENTION_TIME=${PROMETHEUS_RETENTION_TIME:-15d}
      - TZ=${TZ:-Asia/Kolkata}
    volumes:
      - app_data:/prometheus


volumes:
  app_data:

2. Required Environment Variables

VariableDefault / ExampleDescription
PROMETHEUS_RETENTION_TIME15dHow long time-series samples are retained on disk.
TZAsia/KolkataTimezone for Prometheus UI evaluation graphs.

Prometheus Time-Series Monitoring Self-Hosting FAQs

How much RAM is required to self-host Prometheus Time-Series Monitoring in production?

Prometheus Time-Series Monitoring requires a minimum of 1 GB RAM (Pro recommended). On Vexlo Cloud Pro (₹149/mo via UPI in India or $5/mo globally), you get 2 vCPU, 3 GB RAM, and 2 managed databases—more than enough headroom for production workloads.

How do I expose Prometheus Time-Series Monitoring with automatic HTTPS/SSL on Vexlo Cloud?

Deploy the prom/prometheus:latest container on Vexlo Cloud, set the exposed port to 9090, and attach your custom domain in the Domains tab. Vexlo automatically provisions and renews Let's Encrypt TLS certificates.

How is persistent data backed up for Prometheus Time-Series Monitoring?

Mount /prometheus to a persistent Docker volume and connect Vexlo Cloud's automated S3 / Cloudflare R2 backup scheduler to snapshot your database daily or weekly.

More 1-Click Docker Templates

View all 25 templates →