Jammonic

Install on a server

Docker Compose

services:
  jammonic:
    image: jambotron/jammonic:latest
    restart: unless-stopped
    ports:
      - "127.0.0.1:8080:8080"
    environment:
      MONITOR_API_KEYS: ${MONITOR_API_KEYS:?set MONITOR_API_KEYS}
      MONITOR_TELEGRAM_BOT_TOKEN: ${MONITOR_TELEGRAM_BOT_TOKEN:-}
      MONITOR_TELEGRAM_CHAT_ID: ${MONITOR_TELEGRAM_CHAT_ID:-}
    volumes:
      - jammonic_data:/data
    mem_limit: 512m

volumes:
  jammonic_data:

Put a reverse proxy with HTTPS in front (Caddy, nginx, Traefik) and send it to port 8080. With Caddy:

status.example.com {
    reverse_proxy 127.0.0.1:8080
}

Memory and start

The JVM takes 75 % of the container limit for its heap; 512 MB is plenty for hundreds of checks. The image ships an AOT cache, so it starts in a few seconds.

Backup

All data — checks, history, settings — is one SQLite file in the volume (/data/monitor.db). Copy the file (or the volume) to back it up. History older than 90 days is removed automatically.

Settings

Variable Meaning
MONITOR_API_KEYS API keys, comma-separated; empty — API and UI closed
MONITOR_DATA_DIR folder of the SQLite database (/data in the image)
MONITOR_CONFIG_FILE YAML file with checks, applied at start (configuration file)
MONITOR_CHECKS_RETRIES how many times a failed probe is repeated before UP turns DOWN (default 2)
MONITOR_CHECKS_RETRY_DELAY pause between the repeats (default 10s)
alerts see Alerts
sign-in see Sign-in