asura

README

A self-contained Go monitoring service with no external runtime dependencies.

Documentation · Quick Start · API Docs · Contributing

---

Asura monitors your infrastructure from a single Go binary backed by SQLite. No Postgres. No Redis. No Node.js. Just scp a binary and go.

Why Asura?

	Asura	Typical alternative
Runtime	Single static binary	Node.js / Java / Python runtime
Database	SQLite compiled in	Requires Postgres, MySQL, or Redis
Binary size	~15 MB	100-500 MB installed
Deploy	scp binary + run	Package manager, runtime install, migrations
RAM	~20 MB idle	Varies — runtime + database overhead

Highlights

Feature
11 protocols	HTTP, TCP, DNS, ICMP, TLS, WebSocket, Command, Docker, Domain (WHOIS), gRPC, MQTT
Assertion engine	9 types -- status code, body text, body regex, JSON path, headers, response time, cert expiry, DNS records
Incidents	Automatic creation, thresholds, ack, recovery
Notifications	Webhook (HMAC-SHA256), Email, Telegram, Discord, Slack, ntfy
Status pages	Multiple public status pages with custom slugs and grouping
Prometheus	/metrics endpoint with per-monitor, incident, and request metrics

---

Web UI

---

Quick Start

git clone https://github.com/y0f/Asura.git && cd Asura && sudo bash install.sh

Installs Go (if needed), builds the binary, creates a systemd service and generates an admin key.

By default Asura binds to 127.0.0.1:8090 — set up a reverse proxy to expose it.

Docker

git clone https://github.com/y0f/Asura.git && cd Asura
cp config.example.yaml config.yaml
docker compose up -d

---

Documentation

Topic
Getting Started	Install via VPS, Docker, or source
Configuration	Config reference, auth, adaptive intervals
Monitors	11 protocols, assertions, heartbeats
Notifications	6 channels, webhook signing, per-monitor routing
Deployment	Production nginx/caddy setup, TLS
API Reference	All endpoints, fields, pagination
Architecture	Pipeline, storage, checker registry

---

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md.

License

MIT