π Welcome to EZMON
EZMON is a next-generation, push-first infrastructure monitoring platform designed natively for serverless environments. Monitor your servers, detect outages instantly, and get notified β all without exposing a single inbound port on your machines.
Whatβs New in v0.1.3? Weβve completely upgraded the documentation engine to Nextra 4, tuned the UI for an OLED dark mode experience, and stabilized the core agent binaries!
β‘ Quick Start
Get your monitoring agent up and running in under a minute.
Step 1: Create a Project
Log in to your EZMON Dashboard and create a new project. Navigate to the Agents tab and click Install New Agent to generate an Agent Token.
Step 2: Run the Installer
Run the following single command on your Linux server. It automatically detects your architecture, downloads the static binary, and sets up the systemd service.
Linux (curl)
curl -fsSL https://ezmon.web.id/install.sh | bash -s -- --token YOUR_AGENT_TOKENStep 3: Verify Status
Return to your EZMON Dashboard. Your server should instantly appear with the status ONLINE, actively streaming CPU, Memory, Disk, Load, and Docker metrics.
π§ Why Push-First?
Traditional monitoring tools require the server (Hub) to actively poll your machines. This requires open inbound ports, complex firewall rules, and struggles with servers behind NATs.
EZMON flips this paradigm:
- Your servers push a lightweight heartbeat and metrics payload to the EZMON Hub every 30 seconds.
- The Hub (hosted on Vercel) receives the data statelessly.
- A background worker (Cloudflare Cron) checks if any server missed its deadline and dispatches alerts.
This architecture ensures your servers remain completely locked down while still enjoying real-time monitoring.
π Explore the Docs
Dive deeper into what EZMON can do for your infrastructure.
Comprehensive setup guide for the Agent, Hub (Vercel), and Worker (Cloudflare).
π Installation GuideLearn about heartbeat monitoring, offline detection, cloud monitors, and notifications.
β¨ Core FeaturesFull REST API reference with request/response schemas for custom integrations.
π API ReferenceSolutions for common issues like 203/EXEC errors or offline agents.
π§ Troubleshooting