nezha-v1

The v1 version is rebuilt to make the UI more modern v1 and v0 are incompatible, the database structure is incompatible, and local account secret login is supported v1 agents use the same key, making batch deployment more convenient Support one-click installation of panels and monitoring services, making operation convenient. Compatible with mainstream systems, including Linux, Windows, macOS, OpenWRT and Group Media. Supports simultaneous monitoring of the status of multiple servers, provides historical network status and latency charts, and monitors the status of web pages, port availability and SSL Certificates. Supports status alarms such as faults and traffic, and can be alerted through various methods such as Telegram, email, and WeChat. Provides APIs to obtain server status and supports WebSSH, DDNS and traffic monitoring. Timing and trigger tasks can be set, and server tasks can be executed in batches. Configuration guide for v1: nezha.wiki/guide/dashboard.html After deployment, please refer to "Use your own domain name to achieve seamless access to applications in Lazy Cat Micro Service on internal and external networks" lazycat.cloud/playground//#/guideline/513 Using Cloudflanged and local area network port forwarding tools, you can build a private operation and maintenance platform to manage your own various devices If you don't map to the external network, you can set it to the lazy cat's app address domain name, and you can also manage devices in the private domain. The configuration file is located in config.yaml under the data file in the application directory