SiroPing in 10 Minutes
A complete walkthrough: from a clean server to a monitored website with an alert, an incident, a recovery and a client-ready report. Great as onboarding and as a sales demo.
You can do all of this on the free demo at `siroping.vietvang.asia` (register → 30-day
1. Install
On a clean Ubuntu server:
sudo apt update && sudo apt install -y python3 python3-venv redis-server
sudo systemctl enable --now redis-server
# copy the release to /opt/siroping, then:
cd /opt/siroping && sudo ./deploy/install.sh
The installer creates the system user, the venv, .env with secrets, migrates the database and
installs the three systemd services.
2. First-time setup
Open https://<your-server>/setup/ and create the first admin. SiroPing creates your
workspace and logs you into the dashboard. Verify the stack:
sudo -u siroping /opt/siroping/venv/bin/python /opt/siroping/manage.py doctor
On a fresh install `WARNING` is expected until SMTP/ALLOWED_HOSTS/a monitor are set.
3. Add your first website
New HTTP Monitor → name it, enter https://example.com, keep defaults, save. Within the
interval the first check runs and the monitor turns Up (green).
4. Simulate a failure
Point the monitor at a URL that returns a bad status (e.g. change it to a 500, or stop the site). After the failure threshold SiroPing opens an incident and sends an alert to your configured channel (Email / Telegram / Webhook).
5. Receive the alert
Set up one channel in Settings → Notifications, then in Test notification send a test. Confirm the alert arrives on your phone/email.
6. Acknowledge (ACK)
Open the incident and click ACK — the team now knows someone is handling it
(acknowledged_at/by is recorded). No more duplicate noise.
7. Recover
Fix the site (or point the monitor back at a working URL). The next successful check resolves the incident and (if enabled) sends the recovery alert. Uptime starts counting up again.
8. Check health
Open Reports → pick 7/30/90 days → your project. You'll see uptime %, downtime, incidents, MTTR, response time, SSL health and a Health Score (A–F with reasons).
9. Generate a client report
Project → Monthly Report → pick a month → Print → Save as PDF. A branded, white-label report you can send straight to the client (Business adds your logo/company).
10. Publish a status page
Project → Status Page → enable + set slug → share https://<your-server>/status/<slug>/.
Clients can check status without logging in; internal URLs, tokens and config are never exposed.
That's a full monitor → incident → alert → ACK → recovery → report → status loop in about ten minutes. Move to your own server anytime with Migration.