Nezha Monitoring
Server probe and monitoring dashboard (Nezha).
Category MonitoringPlatforms Linux · multi-archPrivileges Effectively needs rootChinese docs Chinese authorStars ~10K
One-click install command
No official one-click command was verified in this round, so none is pasted here. Install from the official repo docs for now.
Notes
No official install command found in this round; don't improvise one — don't present it as one-click until filled in.
Agent Prompt
Copy the block below and hand it to an AI Agent — replace [bracketed] parts with your own values.
Deploy Nezha Monitoring (Server probe and monitoring dashboard (Nezha)) in my environment. Before starting: 1. Run read-only checks first: OS version, CPU architecture, available disk/RAM, port usage, Docker or sudo access — and report the findings. 2. Use the project source https://github.com/nezhahq/nezha as ground truth; verify the current stable version, prerequisites and compatibility. 3. Present an execution plan, the files/services/firewall rules to be changed, and a complete rollback plan; wait for my confirmation before executing. 4. Download remote scripts locally for review first; pin tag / image digest / commit; don't rely on latest or master. 5. Never put secrets (passwords, API keys, tokens, subscription URLs) in the prompt, shell history or logs — use 600-permission env files, Docker secrets or _FILE variables instead. No official one-click command was verified in this round. Base the steps strictly on the official repo docs; do not improvise scripts from unknown sources. Project-specific notes: - No official install command found in this round; don't improvise one — don't present it as one-click until filled in. - Permission requirement: Effectively needs root. Don't escalate privileges; don't run containers as root unnecessarily. After execution, verify and report back: - Installed version, service status and health check results; - Open ports, listen addresses, firewall changes; - Config files, data volumes, log and backup locations; - Access method (for sensitive credentials, only state where they're stored — never print them); - Restart policy, plus verified uninstall / rollback commands.