ChaosOps

Download the package

Choose the archive for your server's CPU architecture (linux-x86_64 for most servers, linux-aarch64 for ARM servers) and save it to your server.

Extract the files

Run tar -xzf chaosops-free-v1.0.0-linux-x86_64.tar.gz to extract it.

Run the installer

Run sudo ./install-server.sh. The installer handles everything automatically.

Save the admin password

After installation, copy the line Default admin: admin / xxxxxxxx — it is shown only once.

Verify the service

Open http://your-server-ip:8000/health in your browser. If you see {status:ok}, the service is running.

Log in to the console

Open http://your-server-ip:8000, sign in with admin and the password you saved. Change the password on first login.

Docker deployment (optional)

Run docker load -i chaosops-free-docker-v0.1.0.tar.gz && docker run -d -p 8000:8000 -v chaosops-data:/opt/chaosops/data chaosops-free:v0.1.0.

Uninstall

Run sudo ./install-server.sh uninstall. The data directory is kept by default; delete it manually to fully remove ChaosOps.

Activate your license (Professional)

Go to Settings → License, enter the activation code from your purchase email (starts with lic_) and confirm. Activation requires internet access once; afterwards the product works offline permanently. For air-gapped servers, download the license file from the activation page and upload it manually.

Add your first server

Go to Nodes → Add Node → copy the install command → run it on the target server.

Expected: The target server appears in the node list with status Online.

Tip: If the command fails, check that the target server can reach the ChaosOps server on port 8000.

Check server status

Open the Dashboard to see node cards, alert stats and recent events.

Expected: Green = healthy, red = critical, yellow = warning but not yet handled.

Tip: Click a node card to view detailed metric curves.

Create an alert rule

Go to Alert Rules → New Rule → pick a metric and threshold → save.

Expected: The rule takes effect immediately and triggers alerts when the metric is abnormal.

Tip: Start with a test rule (e.g. CPU > 1%) to confirm notifications work before adjusting thresholds.

Handle an incident

Open Incidents → click an incident → review the timeline and related nodes → mark as resolved.

Expected: The incident status changes to Resolved and the timeline is preserved.

Tip: Check the AI root-cause analysis before marking as resolved to understand what happened.

Use AI analysis

Open an incident → check the AI root-cause panel → review confidence and suggestions → approve or reject.

Expected: AI provides a root-cause guess, confidence score and suggested actions.

Tip: AI suggestions are for reference only. Manual review is recommended when confidence is below 70%.

Run self-healing

Go to Heal Tasks → pick a pending task → click Confirm → view the result.

Expected: The task status changes to Success and the linked incident is auto-resolved.

Tip: Preview the script before confirming to ensure it is safe to run.

Set up notifications

Open Notification Channels → choose DingTalk, WeCom or email → enter the webhook or address → send a test.

Expected: A test message is successfully delivered to the channel.

Tip: DingTalk and WeCom webhooks are obtained by adding a bot in the group. See the Beginner Guide for details.

Invite your team

Go to Users → Add User → set a role (admin or viewer) → save.

Expected: The new user can log in with the account and password.

Tip: Give non-technical members the Viewer role so they can only read, not operate.

What is a server IP and how to find it

The server IP is its network address. On Linux run ip addr or ifconfig; on Windows run ipconfig. Use this IP in http://your-server-ip:8000 when deploying ChaosOps.

What is a port and how to open it

A port is an entry point for services. ChaosOps uses port 8000 by default. If the page won't open, allow port 8000 in the firewall: sudo ufw allow 8000 or sudo firewall-cmd --add-port=8000/tcp on Linux; also check your cloud security group.

What is sudo and why use it

sudo means "run as administrator" on Linux. It is needed for installing software or changing system settings. Prepend sudo to the command and enter your password. On Windows, right-click and choose "Run as administrator" instead.

What is a Webhook and where to get it

A webhook is a URL that ChaosOps uses to send alerts to your DingTalk or WeCom group. Get it by: opening the group → Group Settings → Assistant → Add Bot → Custom → copy the Webhook URL.

DingTalk notification setup

Open your DingTalk group → Group Settings → Assistant → Add Bot → Custom → copy the Webhook URL → paste it into ChaosOps Notification Channels → DingTalk → save and test. Set a keyword for the bot (e.g. "alert").

WeCom notification setup

Open your WeCom group → top-right ... → Add Group Bot → copy the Webhook URL → paste it into ChaosOps Notification Channels → WeCom → save and test.

Email notification setup

Go to Notification Channels → Email → fill in the SMTP server (e.g. smtp.exmail.qq.com), port (465 or 587), account and password/auth code → save and test. For QQ or NetEase mail, enable SMTP in settings and get an auth code.

AI model setup

Go to Settings → AI Analysis → choose a model type (OpenAI / local model) → enter the API key or local endpoint → save. If you don't have an AI service, you can disable AI analysis; basic monitoring still works.

Database setup

ChaosOps uses built-in SQLite by default. To switch to PostgreSQL, edit data/.env in the install directory and set DATABASE_URL to postgresql://user:pass@host:5432/chaosops, then restart the service.

Backup and restore

Go to Settings → Backup Management → click Create Backup to save all config and data. To restore, upload the backup file. We recommend weekly backups; files are stored in data/backups/.