IPMI Monitor

Free, self-hosted IPMI/BMC monitoring for your server fleet. Collect System Event Logs (SEL), monitor sensors, track ECC errors, and get alerts - all from a beautiful web dashboard.

📸 Screenshots

Fleet Management - Unified service dashboard	IPMI Dashboard - Server status and events
Live Sensors - Temperature, fans, voltage	Hardware Inventory - CPU, Memory, GPU, Storage
Grafana - GPU temps, fans, power, VRAM, throttle	Vast.ai Dashboard - Earnings, GPU usage, power

✨ Features

Core Features

• 🔍 Event Collection - Automatically collect IPMI SEL logs (parallel, 32 workers)
• 📊 Real-time Dashboard - Auto-refreshing every second with server status cards
• 🌡️ Sensor Monitoring - Temperature, fan, voltage, power readings
• 💾 ECC Memory Tracking - Identify which DIMM has errors
• 🎮 GPU Health Monitoring - Detect NVIDIA GPU errors via SSH (Xid errors)
• 📜 SSH System Logs - Collect dmesg, journalctl, syslog, mcelog, Docker daemon logs via SSH
• 🖥️ Vast.ai/RunPod Logs - Auto-collect daemon logs when deployed with DC Overview
• 🔧 Hardware Error Detection - AER, PCIe, ECC errors parsed automatically
• 🔄 Uptime & Reboot Detection - Track unexpected server reboots
• 🚨 Alert Rules - Configurable alerts with email, Telegram, webhooks
• 📈 Prometheus Metrics - Native /metrics endpoint for Grafana
• 🔐 User Management - Admin, read-write, and read-only access levels
• 📥 Full Backup/Restore - Export everything: servers, credentials, SSH keys, alerts

New in v1.1.1

• 📦 Setup Wizard - One-command Docker deployment with CryptoLabs Proxy
• 🌐 CryptoLabs Proxy - Unified reverse proxy with Fleet Management landing page
• 🔗 DC Overview Import - Auto-detect and import servers from DC Overview
• 🔐 SSH Key Management - Auto-detect keys, paste content, or generate ED25519 keys
• 📜 SSH Log Collection - Optional during setup (dmesg, syslog, GPU errors)
• 🖥️ Vast.ai/RunPod Logs - Auto-collects daemon logs when deployed via DC Overview with exporters enabled
• 🚀 Initial Data Collection - Fresh installs auto-collect with progress modal
• 🔒 Auto SSL Renewal - Certbot container for automatic Let's Encrypt cert renewal
• 📋 SEL Management - Enable/disable event logging, view SEL info, get SEL time
• 💚 Sensor Highlighting - Changed values pulse green after refresh
• 🏷️ Site Name Branding - Configure site name via DC Overview for consistent branding
• 🤖 Optional AI Features - Enable AI-powered insights via Settings → AI Features

---

🚀 Quick Start

Automated Deployment (Recommended)

Deploy everything with a single command using a config file:

# Install from dev branch (latest features)
pip install git+https://github.com/cryptolabsza/cryptolabs-proxy.git@dev --break-system-packages
pip install git+https://github.com/cryptolabsza/ipmi-monitor.git@dev --break-system-packages

# Deploy with config file (no prompts)
sudo ipmi-monitor setup -c /path/to/config.yaml -y

See examples/ipmi-config.yaml for a complete config template.

Interactive Setup

Ubuntu 24.04+ / Python 3.12+ (uses pipx):

apt install pipx -y && pipx ensurepath
source ~/.bashrc
pipx install ipmi-monitor
sudo ipmi-monitor setup

Ubuntu 22.04 / Python 3.10:

pipx install ipmi-monitor
sudo ipmi-monitor setup

Note: This automatically deploys cryptolabs-proxy as the unified entry point and authentication layer.

That's it! Answer a few questions and Docker containers are deployed automatically:

╭──────────────────────────────────────────────────╮
│           IPMI Monitor - Quick Setup             │
│                                                  │
│   Deploys via Docker with automatic updates.    │
╰──────────────────────────────────────────────────╯

✓ Docker is installed
✓ DC Overview detected!

? Import server IPs and SSH keys from DC Overview? [Y/n]: y
✓ Found 3 servers from DC Overview
✓ Copied 1 SSH keys from DC Overview

Link BMC IPs to Imported Servers:
  BMC IP for master (Server: 192.168.1.100): 192.168.1.83
  ✓ master: 192.168.1.83
  BMC IP for wk01 (Server: 192.168.1.101): 192.168.1.85
  ✓ wk01: 192.168.1.85

Step 1: Add Servers to Monitor
? How do you want to add servers? Use imported servers only (3 servers)

Step 2-4: Web Settings, Password, AI Features...

Step 5: Auto-Updates
? Enable automatic updates? (recommended) [Y/n]: y

Step 5b: SSH Log Collection (Optional)
? Enable SSH log collection? [y/N]: y

Step 6: Image Channel
? Docker image channel: stable (latest)

Step 7: HTTPS Access (Optional)
? Set up HTTPS reverse proxy? [Y/n]: y
? Domain name: ipmi.example.com
? Use Let's Encrypt? [Y/n]: y

Step 8: Deploying IPMI Monitor
  ✓ SSH key copied: default-key
  ✓ Server configuration saved
  ✓ Docker Compose configuration saved
  ✓ Self-signed certificate generated
  ✓ IPMI Monitor image pulled
  ✓ CryptoLabs Proxy image pulled
  ✓ IPMI Monitor started
  ✓ Let's Encrypt certificate obtained

╭──────────────────────────────────────────────────╮
│              ✓ Setup Complete!                   │
╰──────────────────────────────────────────────────╯
Web Interface: https://ipmi.example.com/
Servers Monitored: 3
HTTPS: Enabled ✓
Auto-Updates: Enabled ✓ (Watchtower)

After Setup

# Check container status
ipmi-monitor status

# View logs
ipmi-monitor logs -f

# Upgrade to latest version
ipmi-monitor upgrade

# Stop/start containers
ipmi-monitor stop
ipmi-monitor start

# Direct Docker commands
docker logs ipmi-monitor
docker restart ipmi-monitor

Bulk Import (Many Servers)

During setup, choose "Import from file" or "Paste text" to add multiple servers at once.

Create a servers.txt file:

# servers.txt - Example server list
# Lines starting with # are comments

# Set global credentials (applied to all servers below)
globalSSH:root,sshpassword
globalIPMI:ADMIN,ipmipassword

# Server list: serverIP,bmcIP (or just serverIP if same)
192.168.1.101,192.168.1.80
192.168.1.102,192.168.1.82
192.168.1.103,192.168.1.84

Then run setup and select "Import from file":

sudo ipmi-monitor setup
# Select: "Import from file (e.g., servers.txt)"
# Enter path: /root/servers.txt

Alternative formats:

SSH only (no IPMI):

global:root,sshpassword
192.168.1.101
192.168.1.102

Per-server credentials:

# serverIP,sshUser,sshPass,ipmiUser,ipmiPass,bmcIP
192.168.1.101,root,pass1,ADMIN,ipmi1,192.168.1.80
192.168.1.102,root,pass2,ADMIN,ipmi2,192.168.1.82

---

🔗 Full Datacenter Suite

For complete GPU datacenter monitoring, combine with DC Overview:

# On master server - install from dev branch
pip install git+https://github.com/cryptolabsza/cryptolabs-proxy.git@dev --break-system-packages
pip install git+https://github.com/cryptolabsza/dc-overview.git@dev --break-system-packages
pip install git+https://github.com/cryptolabsza/ipmi-monitor.git@dev --break-system-packages

# Deploy dc-overview (includes Grafana + Prometheus + GPU metrics + IPMI Monitor)
sudo dc-overview setup -c /path/to/config.yaml -y

Tool	What it monitors
dc-overview	GPU utilization, temperature, power, CPU, RAM, disk
ipmi-monitor	BMC health, SEL events, ECC errors, sensors, system logs
cryptolabs-proxy	Unified authentication, reverse proxy, landing page

All services are accessed through cryptolabs-proxy which provides unified authentication.

Cross-Tool Config Auto-Detection

When deploying both tools, the second setup automatically reuses configuration from the first — no redundant prompts:

# Scenario A: ipmi-monitor first, dc-overview second
sudo ipmi-monitor setup -c ipmi-config.yaml -y   # Sets up proxy, credentials, servers
sudo dc-overview setup -c dc-config.yaml -y       # Auto-detects proxy credentials, SSL, SSH keys

# Scenario B: dc-overview first, ipmi-monitor second
sudo dc-overview setup -c dc-config.yaml -y       # Sets up proxy, credentials, servers
sudo ipmi-monitor setup -c ipmi-config.yaml -y    # Auto-detects proxy credentials, AI key, site name

What gets auto-detected from an existing proxy:

• Fleet admin credentials (FLEET_ADMIN_USER / FLEET_ADMIN_PASS)
• Site name (SITE_NAME)
• AI / Watchdog license key (WATCHDOG_API_KEY)
• Domain and SSL mode (from nginx config)
• SSH keys and server list (from /etc/ipmi-monitor/ or /etc/dc-overview/)

Priority order (highest to lowest):

Priority	Source	Example
1	Config file (-c)	fleet_admin_pass: mypass in YAML
2	Running proxy env vars	Auto-detected from cryptolabs-proxy container
3	Interactive prompt	Asked if neither of the above provides a value

Note: Config file values always win. If your two config files specify different credentials, each deployment uses its own file's values — the proxy is not silently overridden. The auto-detection only fills in values that are missing from the config file.

DC Inventory Credential Receiver

When IPMI Monitor receives inventory from DC Overview, configure the existing shared inventory secret as a read-only file and set IPMI_INVENTORY_SECRET_FILE to its container path. Do not place that secret in an environment variable or in a request body. DC Overview signs requests with DC-HMAC and encrypts an optional credential bundle with a key derived from that file.

FLEET_CREDENTIAL_AUTHORITY must be either local or vault. IPMI Monitor defaults to vault when IPMI_BMC_CREDENTIALS_FILE is configured, otherwise it defaults to local. Vault mode continues metadata-only inventory sync but rejects credential bundles. Standalone Compose deployments must mount the same secret file read-only into both services and explicitly set the authority.

CLI Commands

# Setup (recommended)
sudo ipmi-monitor setup    # Interactive Docker deployment

# Container management
ipmi-monitor status             # Show container status
ipmi-monitor logs               # View container logs
ipmi-monitor logs -f            # Follow logs
ipmi-monitor stop               # Stop containers
ipmi-monitor start              # Start containers
ipmi-monitor restart            # Restart containers
ipmi-monitor upgrade            # Pull latest image & restart

# Server management
ipmi-monitor add-server         # Add a server interactively
ipmi-monitor list-servers       # List configured servers

# Advanced (for non-Docker setups)
ipmi-monitor setup              # Interactive setup wizard
ipmi-monitor run                # Start web interface directly
ipmi-monitor daemon             # Run as daemon (for systemd)

---

Option 2: Docker Compose

For containerized deployments or if you prefer Docker:

Step 1: Create project directory

mkdir ipmi-monitor && cd ipmi-monitor

Step 2: Create docker-compose.yml:

version: '3.8'

services:
  ipmi-monitor:
    image: ghcr.io/cryptolabsza/ipmi-monitor:latest
    container_name: ipmi-monitor
    restart: unless-stopped
    ports:
      - "5000:5000"
    environment:
      - APP_NAME=My Server Fleet        # Customize this
      - IPMI_USER=admin
      - IPMI_PASS=YOUR_BMC_PASSWORD     # Your BMC password
      - ADMIN_PASS=YOUR_ADMIN_PASSWORD  # CHANGE THIS!
      - SECRET_KEY=YOUR_RANDOM_SECRET_KEY
    volumes:
      - ipmi_data:/app/data             # ⚠️ IMPORTANT: Persists your data!
    labels:
      - "com.centurylinklabs.watchtower.enable=true"  # Enable auto-updates

volumes:
  ipmi_data:

Step 3: Start the service

docker-compose up -d

Step 4: Open http://localhost:5000 and add your servers!

---

Option 3: Docker Run

# Create a named volume for data persistence
docker volume create ipmi_data

# Run the container
docker run -d \
  --name ipmi-monitor \
  --label com.centurylinklabs.watchtower.enable=true \
  -p 5000:5000 \
  -e IPMI_USER=admin \
  -e IPMI_PASS=YOUR_BMC_PASSWORD \
  -e ADMIN_PASS=YOUR_ADMIN_PASSWORD \
  -e SECRET_KEY=YOUR_RANDOM_SECRET_KEY \
  -v ipmi_data:/app/data \
  --restart unless-stopped \
  ghcr.io/cryptolabsza/ipmi-monitor:latest

---

⚠️ Important: Data Persistence

Always use a named volume to preserve your data across container updates:

# ✅ CORRECT - Named volume (survives updates)
volumes:
  - ipmi_data:/app/data

# ❌ WRONG - No volume (data lost on rebuild)
# (no volume specified)

---

📁 Configuration File Reference

servers.yaml

servers:
  - name: GPU-Server-01           # Display name
    bmc_ip: 192.168.1.80          # BMC/IPMI IP (required)
    username: admin               # BMC username
    password: YOUR_BMC_PASSWORD   # BMC password
    protocol: auto                # auto, ipmi, or redfish
    
    # Optional: SSH for system logs
    server_ip: 192.168.1.81       # Server OS IP
    ssh_user: root
    ssh_port: 22
    ssh_password: YOUR_SSH_PASSWORD  # Or use ssh_key
    ssh_key: ~/.ssh/id_rsa           # Path to SSH private key

config.yaml

settings:
  web_port: 5000
  refresh_interval: 60           # Seconds between collections
  enable_prometheus: true        # /metrics endpoint

ai:
  enabled: false                 # Enable AI features
  license_key: sk-ipmi-xxxx      # CryptoLabs license key

---

🔄 Keeping Up to Date

Setup Deployment (Recommended)

If you used sudo ipmi-monitor setup with the HTTPS proxy (cryptolabs-proxy), updates are automatic via cryptolabs-watchtower (deployed by cryptolabs-proxy):

# Check for updates manually
ipmi-monitor upgrade

# Or just wait - cryptolabs-watchtower checks every 5 minutes

CLI Update

pipx upgrade ipmi-monitor

Docker Manual Update

# Pull the latest image
docker pull ghcr.io/cryptolabsza/ipmi-monitor:latest

# Recreate the container (preserves data volume)
cd /etc/ipmi-monitor && docker compose up -d

Automatic Updates with cryptolabs-watchtower

cryptolabs-proxy deploys cryptolabs-watchtower when the proxy is configured. When using setup with HTTPS, auto-updates are included. For manual setups with cryptolabs-proxy, run cryptolabs-proxy setup to get both proxy and watchtower. Other services (dc-overview, ipmi-monitor) add the label so cryptolabs-watchtower can update them:

services:
  ipmi-monitor:
    # ... your existing config ...
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

Tag	Description
:latest	Latest stable release (recommended)
:develop	Development builds (testing new features)
:v1.1.1	Specific version (pin for stability)

---

🔍 Troubleshooting

Container won't start

# Check logs
docker logs ipmi-monitor

# Common issues:
# - Port 5000 already in use: Change port mapping to "5001:5000"
# - Permission denied: Ensure docker socket access

Can't connect to BMC

# Test from the container
docker exec ipmi-monitor ipmitool -I lanplus -H 192.168.1.80 -U admin -P password power status

# Common issues:
# - Wrong IP address (use BMC IP, not server OS IP)
# - Firewall blocking port 623 (IPMI)
# - Wrong credentials

SSH inventory collection fails

# Test SSH from container
docker exec ipmi-monitor ssh -o StrictHostKeyChecking=no root@192.168.1.81 hostname

# Common issues:
# - SSH key not added to container (add via Settings → SSH Keys)
# - Server IP not set (only BMC IP configured)
# - Firewall blocking port 22

Data disappeared after update

Your volume name must match! Check with:

docker volume ls | grep ipmi

If you see multiple volumes (e.g., ipmi_data and ipmi-monitor_ipmi_data), you may have used different names. Restore by:

docker stop ipmi-monitor
docker run --rm -v OLD_VOLUME:/from -v NEW_VOLUME:/to alpine cp -av /from/. /to/

---

⚙️ Environment Variables (Docker)

Variable	Default	Description
APP_NAME	IPMI Monitor	Displayed in header
IPMI_USER	admin	Default BMC username
IPMI_PASS	(required)	Default BMC password
IPMI_PASS_NVIDIA	-	Separate password for NVIDIA DGX BMCs (16-char requirement)
ADMIN_USER	admin	Dashboard admin username
ADMIN_PASS	changeme	Dashboard admin password (change this!)
SECRET_KEY	(auto)	Flask session secret (set this for persistent sessions!)
POLL_INTERVAL	300	Seconds between collections
DATA_RETENTION_DAYS	30	How long to keep events
SSH_USER	root	Default SSH username for system log collection
SSH_PASS	-	Default SSH password (or use SSH keys)
SITE_NAME	IPMI Monitor	Site name for branding (set via DC Overview)
ENABLE_SSH_LOGS	false	Enable SSH log collection
COLLECT_VASTAI_LOGS	false	Collect Vast.ai daemon logs (auto-set by DC Overview)
COLLECT_RUNPOD_LOGS	false	Collect RunPod agent logs (auto-set by DC Overview)

---

🔧 Setting Up SSH for Enhanced Monitoring

SSH access enables powerful features:

• System Logs - dmesg, journalctl, syslog, Docker daemon logs
• GPU Platform Logs - Vast.ai daemon and RunPod agent logs (when enabled)
• Hardware Inventory - Detailed CPU, DIMM, GPU, NIC, storage info
• GPU Monitoring - NVIDIA Xid errors, driver version, CUDA version
• Uptime Tracking - Detect unexpected reboots

Note: When deployed via dc-overview setup with Vast.ai or RunPod exporters enabled, IPMI Monitor automatically collects platform-specific daemon logs.

Option 1: SSH Keys (Recommended)

1. Go to Settings → SSH Keys
2. Click Add SSH Key
3. Paste your private key content (from ~/.ssh/id_rsa or similar)
4. Give it a name (e.g., "datacenter-key")
5. In Settings → Servers, assign the key to each server

Option 2: SSH Password

1. Go to Settings → Defaults
2. Enter your SSH username and password
3. Click Apply to All Servers

Important: Server IP vs BMC IP

• BMC IP (e.g., 192.168.1.80) - IPMI/Redfish management interface
• Server IP (e.g., 192.168.1.81) - The actual OS/SSH interface

When adding a server, set both IPs:

• BMC IP: For IPMI/Redfish event collection
• Server IP: For SSH-based inventory and logs

---

🎮 GPU Monitoring (NVIDIA)

IPMI Monitor can detect and monitor NVIDIA GPUs via SSH:

• GPU Count & Models - Detected via nvidia-smi
• Driver & CUDA Version - For compatibility tracking
• Xid Errors - Parsed from dmesg/syslog (GPU failures, ECC errors)
• PCIe Health - AER/correctable/uncorrectable errors

Collecting GPU Inventory

1. Ensure SSH is configured for the server
2. Go to server detail page
3. Click Collect Inventory
4. GPU info appears under 🎮 GPU section

---

📋 Detailed DIMM Inventory

For servers with Redfish or SSH access, IPMI Monitor collects per-DIMM details:

• Slot/Locator (e.g., A1, B2)
• Manufacturer (Samsung, SK Hynix, Micron, etc.)
• Part Number
• Size (32 GB, 64 GB)
• Speed (Configured vs Rated - highlights if running slower)

This helps identify:

• Mixed memory configurations
• Under-clocked DIMMs
• Which slot has ECC errors

---

🤖 AI Features (Optional)

IPMI Monitor can integrate with the CryptoLabs AI service for:

• Fleet Summary - AI-generated daily analysis
• Predictive Maintenance - Identify failing components
• Root Cause Analysis - Correlate events across servers
• Task Generation - Prioritized maintenance tasks

Enabling AI Features

1. Go to Settings → AI Features
2. Get an API key from cryptolabs.co.za/my-account
3. Enter the key and click Enable

📌 AI features are optional - IPMI Monitor works fully offline without them.

---

🔌 IPMI vs Redfish

IPMI Monitor supports both protocols and auto-detects which to use:

Feature	IPMI/ipmitool	Redfish
Event Collection	✅ SEL logs	✅ Log Service
Sensor Readings	✅ SDR	✅ Chassis/Thermal
Power Control	✅	✅
Inventory	Basic FRU	✅ Rich metadata
Memory Details	-	✅ Per-DIMM info
Supported BMCs	All	Dell iDRAC, HPE iLO, Supermicro, Lenovo

Forcing a Protocol

By default, IPMI Monitor auto-detects. To force a specific protocol:

1. Go to Settings → Servers
2. Click Edit on a server
3. Set Protocol to ipmi or redfish

---

🚨 Alert Configuration

IPMI Monitor can send alerts via multiple channels:

Notification Methods

Method	Setup
Email	Settings → Alerts → SMTP configuration
Telegram	Settings → Alerts → Bot token + Chat ID
Webhook	Settings → Alerts → Custom URL for Slack, Discord, etc.

Alert Rules

Create rules to trigger on specific conditions:

• Event Type - SEL event categories (Temperature, Memory, Fan, etc.)
• Severity - Critical, Warning, or both
• Server Filter - All servers or specific ones
• Keyword Match - Filter by event description

Alert Features

• Confirmation Period - Wait N minutes before alerting (avoid false positives)
• Resolution Alerts - Get notified when issues are resolved
• Rate Limiting - Prevent alert floods

---

📋 API Reference

Public Endpoints

Endpoint	Description
GET /	Dashboard
GET /api/servers	List servers
GET /api/events	Get events (filterable)
GET /api/stats	Dashboard stats
GET /api/sensors/{bmc_ip}	Sensor readings
GET /metrics	Prometheus metrics
GET /health	Health check
GET /api/version	Current version info
GET /api/version/check	Check for updates
POST /api/server/{bmc_ip}/bmc/{action}	BMC reset (cold/warm/info)
GET /api/server/{bmc_ip}/ssh-logs	Get SSH system logs

Admin Endpoints (login required)

Endpoint	Description
POST /api/collect	Trigger collection
POST /api/servers/add	Add server
DELETE /api/servers/{bmc_ip}	Delete server
GET /api/backup	Full configuration backup
POST /api/restore	Restore from backup

---

🔒 Security

IPMI Monitor is designed with security in mind for production datacenter environments:

Credential Protection

• No Command-Line Exposure - IPMI passwords use environment variables (IPMI_PASSWORD), not -P flags
• SSH Key Isolation - SSH private keys stored in temporary files with 0600 permissions
• Password Masking - Passwords passed via SSHPASS environment variable, not command line

Data Handling

• Local-First - All data stored locally in SQLite
• No Credential Sync - Credentials are never sent externally

Access Control

• Role-Based Access - Admin vs read-only user levels
• Session Management - Secure Flask sessions with configurable secret key
• API Authentication - Protected endpoints require authentication

Best Practices

environment:
  - SECRET_KEY=your-random-32-char-key  # Always set this!
  - ADMIN_PASS=strong-unique-password   # Change from default

---

🔑 Password Recovery

IPMI Monitor is self-hosted - there's no central server to reset your password. Since you have root access, you can reset it directly:

# Quick password reset (run on your server)
docker exec -i ipmi-monitor python3 << 'EOF'
from werkzeug.security import generate_password_hash
import sqlite3
new_password = "your_new_password"  # CHANGE THIS
conn = sqlite3.connect('/var/lib/ipmi-monitor/ipmi_events.db')
conn.execute("UPDATE user SET password_hash = ? WHERE username = 'admin'", 
             (generate_password_hash(new_password),))
conn.commit()
print(f"✅ Admin password updated!")
EOF

📖 See User Guide - Password Recovery for detailed instructions and a reusable script.

---

📊 Development Status

Implemented Features ✓

Feature	Status
Core IPMI monitoring	✓ Complete
AI-powered insights	✓ Complete
CryptoLabs SSO integration	✓ Complete
API key validation	✓ Complete
402 Payment Required handling	✓ Complete (in alerts.py)

Pending Features (In Development)

Feature	Status
401 Unauthorized UI prompt ("Re-link Account")	⏳ Pending
Subscription expiry warning banner	⏳ Pending
API key rotation detection	⏳ Pending

---

🛠️ Developer Guide

See DEVELOPER_GUIDE.md for:

• Git workflow (develop/main branches)
• Release process
• Docker tag conventions
• CI/CD pipeline details

---

🤝 Contributing

1. Fork the repository
2. Create feature branch (git checkout -b feature/amazing)
3. Commit changes (git commit -m 'Add amazing feature')
4. Push to branch (git push origin feature/amazing)
5. Open a Pull Request

---

📜 License

MIT License - see LICENSE for details.

---

🔗 Links

• PyPI: pypi.org/project/ipmi-monitor
• GitHub: github.com/cryptolabsza/ipmi-monitor
• Docker Image: ghcr.io/cryptolabsza/ipmi-monitor
• Documentation: CryptoLabs Support
• Discord Community: Join our Discord - Get help, report issues, request features

---

Made with ❤️ by CryptoLabs