Let the Agent start/on-line, and the self-test process of the problem #
Run //opt/nezha/agent/nezha-agent -s IP/Domin(Panel IP or Domain not connected to CDN):port(Panel RPC port) -p secret(Agent Secret) -d Check the logs to see if the timeout is due to a DNS problem or poor network
nc -v domain/IP port(Panel RPC port) or telnet domain/IP port(Panel RPC port) to check if it' s a network problem, check the inbound and outbound firewall between the local machine and the panel server, if you can' t determine the problem you can check it with the port checking tool provided by https://port.ping.pe/
If the above steps work and the Agent is online, please try to turn off SELinux on the panel server. How to close SELinux\uFF1F
',2),s=[a];function l(i,c,h,p,d,_){return o(),t("div",null,s)}var u=e(r,[["render",l]]);export{m as __pageData,u as default};
diff --git a/assets/en_US_guide_q2.md.a230a9b9.lean.js b/assets/en_US_guide_q2.md.a230a9b9.lean.js
new file mode 100644
index 00000000..aca1361b
--- /dev/null
+++ b/assets/en_US_guide_q2.md.a230a9b9.lean.js
@@ -0,0 +1 @@
+import{_ as e,c as t,o,d as n}from"./app.2c402e15.js";const m='{"title":"Let the Agent start/on-line, and the self-test process of the problem","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q2.md"}',r={},a=n("",2),s=[a];function l(i,c,h,p,d,_){return o(),t("div",null,s)}var u=e(r,[["render",l]]);export{m as __pageData,u as default};
diff --git a/assets/en_US_guide_q2.md.d1c860d2.js b/assets/en_US_guide_q2.md.d1c860d2.js
deleted file mode 100644
index 77d4fdd1..00000000
--- a/assets/en_US_guide_q2.md.d1c860d2.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q2.md"}',s={},r=o("p",null,"q2",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q2.md.d1c860d2.lean.js b/assets/en_US_guide_q2.md.d1c860d2.lean.js
deleted file mode 100644
index 77d4fdd1..00000000
--- a/assets/en_US_guide_q2.md.d1c860d2.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q2.md"}',s={},r=o("p",null,"q2",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q3.md.4782ed4a.js b/assets/en_US_guide_q3.md.4782ed4a.js
deleted file mode 100644
index 3d4703e4..00000000
--- a/assets/en_US_guide_q3.md.4782ed4a.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q3.md"}',s={},r=o("p",null,"q3",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q3.md.4782ed4a.lean.js b/assets/en_US_guide_q3.md.4782ed4a.lean.js
deleted file mode 100644
index 3d4703e4..00000000
--- a/assets/en_US_guide_q3.md.4782ed4a.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q3.md"}',s={},r=o("p",null,"q3",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q3.md.8d0aa8e5.js b/assets/en_US_guide_q3.md.8d0aa8e5.js
new file mode 100644
index 00000000..528af27f
--- /dev/null
+++ b/assets/en_US_guide_q3.md.8d0aa8e5.js
@@ -0,0 +1,25 @@
+import{_ as e,c as n,o as a,d as s}from"./app.2c402e15.js";const g='{"title":"Reverse Proxy gRPC Port (support Cloudflare CDN)","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q3.md"}',t={},o=s(`
Reverse Proxy gRPC Port (support Cloudflare CDN) #
Use Nginx or Caddy to reverse proxy gRPC
Nginx configuration files
server{
+ listen443 ssl http2;
+ listen [::]:443 ssl http2;
+ server_name data.example.com;# The domain name where the Agent connects to Dashboard
+
+ ssl_certificate /data/letsencrypt/fullchain.pem;# Your domain certificate path
+ ssl_certificate_key /data/letsencrypt/key.pem;# Your domain's private key path
+
+ underscores_in_headerson;
+
+ location /{
+ grpc_read_timeout300s;
+ grpc_send_timeout300s;
+ grpc_pass grpc://localhost:5555;
+ }
+}
+
Caddy configuration files
data.example.com:443 { # The domain name where the Agent connects to Dashboard
+ reverse_proxy {
+ to localhost:5555
+ transport http {
+ versions h2c 2
+ }
+ }
+}
+
Dashboard Configuration
First login to the Dashboard and enter the admin panel, go to the settings page, fill in the CDN Bypassed Domain/IP with the domain name you configured in Nginx or Caddy, for example data.example.com, and save it.
Then open the /opt/nezha/dashboard/data/config.yaml file in the panel server and change proxygrpcport to the port that Nginx or Caddy is listening on, such as 443 as set in the previous step. Since we have SSL/TLS enabled in Nginx or Caddy, we need to set tls to true, restart the panel when you are done.
Agent Configuration
Log in to the admin panel, copy the one-click install command, and run the one-click install command on the corresponding server to reinstall the agent.
Enable Cloudflare CDN (optional)
According to Cloudflare gRPC requirements: gRPC services must listen on port 443 and must support TLS and HTTP/2. So if you need to enable CDN, you must use port 443 when configuring Nginx or Caddy reverse proxy gRPC and configure the certificate (Caddy will automatically apply and configure the certificate).
Log in to Cloudflare and select the domain you are using. Go to the Network page and turn on the gRPC switch, then go to the DNS page, find the resolution record of the domain with gRPC configuration, and turn on the orange cloud icon to enable CDN.
`,13),p=[o];function c(r,i,l,d,u,h){return a(),n("div",null,p)}var m=e(t,[["render",c]]);export{g as __pageData,m as default};
diff --git a/assets/en_US_guide_q3.md.8d0aa8e5.lean.js b/assets/en_US_guide_q3.md.8d0aa8e5.lean.js
new file mode 100644
index 00000000..fb01560e
--- /dev/null
+++ b/assets/en_US_guide_q3.md.8d0aa8e5.lean.js
@@ -0,0 +1 @@
+import{_ as e,c as n,o as a,d as s}from"./app.2c402e15.js";const g='{"title":"Reverse Proxy gRPC Port (support Cloudflare CDN)","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q3.md"}',t={},o=s("",13),p=[o];function c(r,i,l,d,u,h){return a(),n("div",null,p)}var m=e(t,[["render",c]]);export{g as __pageData,m as default};
diff --git a/assets/en_US_guide_q4.md.21280a24.js b/assets/en_US_guide_q4.md.21280a24.js
deleted file mode 100644
index 246ab6c4..00000000
--- a/assets/en_US_guide_q4.md.21280a24.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q4.md"}',s={},r=o("p",null,"q4",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q4.md.21280a24.lean.js b/assets/en_US_guide_q4.md.21280a24.lean.js
deleted file mode 100644
index 246ab6c4..00000000
--- a/assets/en_US_guide_q4.md.21280a24.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q4.md"}',s={},r=o("p",null,"q4",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q4.md.62e807a2.js b/assets/en_US_guide_q4.md.62e807a2.js
new file mode 100644
index 00000000..ecceb30e
--- /dev/null
+++ b/assets/en_US_guide_q4.md.62e807a2.js
@@ -0,0 +1 @@
+import{_ as t,c as a,o,a as e,b as n}from"./app.2c402e15.js";const v='{"title":"Real-time channel disconnection/online terminal connection failure","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q4.md"}',i={},r=e("h4",{id:"real-time-channel-disconnection-online-terminal-connection-failure",tabindex:"-1"},[n("Real-time channel disconnection/online terminal connection failure "),e("a",{class:"header-anchor",href:"#real-time-channel-disconnection-online-terminal-connection-failure","aria-hidden":"true"},"#")],-1),c=e("ul",null,[e("li",null,"If you are using a CDN, please make sure that the CDN provider provides WebSocket service and that WebSocket is enabled"),e("li",null,[n("Confirm that you are using a reverse proxy requires special configuration of the WebSocket for the "),e("code",null,"/ws"),n(" and "),e("code",null,"/terminal"),n(" paths, you can "),e("a",{href:"/en_US/guide/dashboard.html#configure-reverse-proxy"},"click here"),n(" to see the reverse proxy configuration")])],-1),l=[r,c];function s(d,u,h,f,_,m){return o(),a("div",null,l)}var g=t(i,[["render",s]]);export{v as __pageData,g as default};
diff --git a/assets/en_US_guide_q4.md.62e807a2.lean.js b/assets/en_US_guide_q4.md.62e807a2.lean.js
new file mode 100644
index 00000000..ecceb30e
--- /dev/null
+++ b/assets/en_US_guide_q4.md.62e807a2.lean.js
@@ -0,0 +1 @@
+import{_ as t,c as a,o,a as e,b as n}from"./app.2c402e15.js";const v='{"title":"Real-time channel disconnection/online terminal connection failure","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q4.md"}',i={},r=e("h4",{id:"real-time-channel-disconnection-online-terminal-connection-failure",tabindex:"-1"},[n("Real-time channel disconnection/online terminal connection failure "),e("a",{class:"header-anchor",href:"#real-time-channel-disconnection-online-terminal-connection-failure","aria-hidden":"true"},"#")],-1),c=e("ul",null,[e("li",null,"If you are using a CDN, please make sure that the CDN provider provides WebSocket service and that WebSocket is enabled"),e("li",null,[n("Confirm that you are using a reverse proxy requires special configuration of the WebSocket for the "),e("code",null,"/ws"),n(" and "),e("code",null,"/terminal"),n(" paths, you can "),e("a",{href:"/en_US/guide/dashboard.html#configure-reverse-proxy"},"click here"),n(" to see the reverse proxy configuration")])],-1),l=[r,c];function s(d,u,h,f,_,m){return o(),a("div",null,l)}var g=t(i,[["render",s]]);export{v as __pageData,g as default};
diff --git a/assets/en_US_guide_q5.md.0a1d56d0.js b/assets/en_US_guide_q5.md.0a1d56d0.js
new file mode 100644
index 00000000..563e6283
--- /dev/null
+++ b/assets/en_US_guide_q5.md.0a1d56d0.js
@@ -0,0 +1 @@
+import{_ as a,c as r,o,a as e,b as t}from"./app.2c402e15.js";const f='{"title":"How do I migrate my data to the new server and restore my backups?","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q5.md"}',s={},n=e("h4",{id:"how-do-i-migrate-my-data-to-the-new-server-and-restore-my-backups",tabindex:"-1"},[t("How do I migrate my data to the new server and restore my backups? "),e("a",{class:"header-anchor",href:"#how-do-i-migrate-my-data-to-the-new-server-and-restore-my-backups","aria-hidden":"true"},"#")],-1),c=e("ol",null,[e("li",null,[t("First use the one-click script and select "),e("code",null,"Stop Panel")]),e("li",null,[t("Compress the "),e("code",null,"/opt/nezha"),t(" folder to the same path as the new server")]),e("li",null,[t("Run the one-click script in the new server, select "),e("code",null,"Launch Panel")])],-1),d=[n,c];function l(i,h,u,m,p,_){return o(),r("div",null,d)}var v=a(s,[["render",l]]);export{f as __pageData,v as default};
diff --git a/assets/en_US_guide_q5.md.0a1d56d0.lean.js b/assets/en_US_guide_q5.md.0a1d56d0.lean.js
new file mode 100644
index 00000000..563e6283
--- /dev/null
+++ b/assets/en_US_guide_q5.md.0a1d56d0.lean.js
@@ -0,0 +1 @@
+import{_ as a,c as r,o,a as e,b as t}from"./app.2c402e15.js";const f='{"title":"How do I migrate my data to the new server and restore my backups?","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q5.md"}',s={},n=e("h4",{id:"how-do-i-migrate-my-data-to-the-new-server-and-restore-my-backups",tabindex:"-1"},[t("How do I migrate my data to the new server and restore my backups? "),e("a",{class:"header-anchor",href:"#how-do-i-migrate-my-data-to-the-new-server-and-restore-my-backups","aria-hidden":"true"},"#")],-1),c=e("ol",null,[e("li",null,[t("First use the one-click script and select "),e("code",null,"Stop Panel")]),e("li",null,[t("Compress the "),e("code",null,"/opt/nezha"),t(" folder to the same path as the new server")]),e("li",null,[t("Run the one-click script in the new server, select "),e("code",null,"Launch Panel")])],-1),d=[n,c];function l(i,h,u,m,p,_){return o(),r("div",null,d)}var v=a(s,[["render",l]]);export{f as __pageData,v as default};
diff --git a/assets/en_US_guide_q5.md.410e46a9.js b/assets/en_US_guide_q5.md.410e46a9.js
deleted file mode 100644
index d7f6585a..00000000
--- a/assets/en_US_guide_q5.md.410e46a9.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q5.md"}',s={},r=o("p",null,"q5",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/assets/en_US_guide_q5.md.410e46a9.lean.js b/assets/en_US_guide_q5.md.410e46a9.lean.js
deleted file mode 100644
index d7f6585a..00000000
--- a/assets/en_US_guide_q5.md.410e46a9.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,c as t,o as a,a as o}from"./app.2c402e15.js";const m='{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/q5.md"}',s={},r=o("p",null,"q5",-1),n=[r];function c(_,d,i,p,l,f){return a(),t("div",null,n)}var h=e(s,[["render",c]]);export{m as __pageData,h as default};
diff --git a/developer/index.html b/developer/index.html
index 8782b8fe..4bc53ae9 100644
--- a/developer/index.html
+++ b/developer/index.html
@@ -14,7 +14,7 @@
Run ./nezha-agent --help to view supported flags，if you are already using the one-click script, you can edit /etc/systemd/system/nezha-agent.service，at the end of this line ExecStart= add:
--report-delay System information reporting interval, default is 1 second, can be set to 3 to reduce the system resource usage on the agent side (configuration range 1-4)
--skip-conn Not monitoring the number of connections, if it is a server with a large number of connections, the CPU usage will be high. It is recommended to set this to reduce CPU usage
--skip-procs Disable monitoring the number of processes can also reduce CPU and memory usage
--disable-command-execute Disable execution of scheduled tasks, disallow WebShell (security feature)
--tls Enable SSL/TLS encryption (If you are using nginx to reverse proxy Agent´s grpc connections, and if nginx has SSL/TLS enabled, you need to enable this configuration)
First, temporarily disable the reverse proxy As with other websites, you can choose to automatically apply for a Let´s Encrypt certificate or manually configure an existing certificate by going to "SSL" in the site settings After you finish setting up SSL, you need to go back to https://github.com/settings/developers and edit the authentication application you created before, change all the domain names in the "Homepage URL" and "Authorization callback URL" you filled in before from http to https, such as: "https://cdn.example.com" and "https://cdn.example.com/oauth2/callback", If you don't change these links, you may not be able to log into the admin panel
Nezha Monitoring supports monitoring of server load, CPU, memory, hard disk, bandwidth, data transfer, monthly data transfer, number of processes, number of connections, and sends alarm notifications when one of these items reaches a user-set limit.
#NEZHA# is the panel message placeholder, the panel will automatically replace the placeholder with the actual message when it triggers the notification
The content of Body is in JSON format：When the request type is FORM，the value is in the form of key:value，value can contain placeholders that will be automatically replaced when notified. When the request type is JSON It will only do string substitution and submit to the URL directly.
Placeholders can also be placed inside the URL, and it will perform a simple string substitution when requested.
URL Parameter acquisition instructions：The XXXXXX in botXXXXXX is the token provided when you follow the official @Botfather in Telegram and enter /newbot to create a new bot. (In the line after Use this token to access the HTTP API). The 'bot' are essential. After creating a bot, you need to talk to the BOT in Telegram (send a random message) before you can send a message by using API. YYYYYY is Telegram user's ID, you can get it by talking to the bot @userinfobot.
Type: one or more types can be selected, such as in a rule to select more than one type, you need to meet all the selected types at the same time to trigger the notification (see the example later)
cpu、memory、swap、disk
net_in_speed Inbound speed, net_out_speed Outbound speed, net_all_speed Inbound + Outbound speed, transfer_in Inbound Transfer, transfer_out Outbound Transfer, transfer_all Total Transfer
offline Offline monitoring
load1、load5、load15 Load
process_count Number of processes Currently, counting the number of processes takes up too many resources and is not supported at the moment
tcp_conn_count、udp_conn_count Number of connections
duration：Lasting for a few seconds, the notification will only be triggered when the sampling record reaches 30% or more within a few seconds
min/max
Transfer, network speed, and other values of the same type. Unit is byte (1KB=1024B，1MB = 1024*1024B)
Memory, hard disk, CPU. units are usage percentages
transfer_in_cycle Inbound transfer during the cycle
transfer_out_cycle Outbound transfer during the cycle
transfer_all_cycle The sum of inbound and outbound transfer during the cycle
cycle_start Start date of the statistical cycle (can be the start date of your server's billing cycle), the time format is RFC3339, for example, the format in Beijing time zone is 2022-01-11T08:00:00.00+08:00
cycle_interval Interval time cycle (For example, if the cycle is in days and the value is 7, it means that the statistics are counted every 7 days)
min/max, cover, ignore Please refer to the basic rules to configure
Example: The server with ID 3 (defined in the ignore) is counted on the 15th of each month, and a notification is triggered when the monthly outbound traffic reaches 1TB during the cycle. [{"type":"transfer_out_cycle","max":1000000000000,"cycle_start":"2022-01-11T08:00:00.00+08:00","cycle_interval":1,"cycle_unit":"month","cover":1,"ignore":{"3":true}}]
diff --git a/en_US/guide/q2.html b/en_US/guide/q2.html
index c5b27916..f8bf1981 100644
--- a/en_US/guide/q2.html
+++ b/en_US/guide/q2.html
@@ -3,18 +3,18 @@
- Nezha Monitoring
+ Let the Agent start/on-line, and the self-test process of the problem | Nezha Monitoring
-
+
-
-
+
+
Let the Agent start/on-line, and the self-test process of the problem #
Run //opt/nezha/agent/nezha-agent -s IP/Domin(Panel IP or Domain not connected to CDN):port(Panel RPC port) -p secret(Agent Secret) -d Check the logs to see if the timeout is due to a DNS problem or poor network
nc -v domain/IP port(Panel RPC port) or telnet domain/IP port(Panel RPC port) to check if it' s a network problem, check the inbound and outbound firewall between the local machine and the panel server, if you can' t determine the problem you can check it with the port checking tool provided by https://port.ping.pe/
If the above steps work and the Agent is online, please try to turn off SELinux on the panel server. How to close SELinux？
Reverse Proxy gRPC Port (support Cloudflare CDN) #
Use Nginx or Caddy to reverse proxy gRPC
Nginx configuration files
server{
+ listen443 ssl http2;
+ listen [::]:443 ssl http2;
+ server_name data.example.com;# The domain name where the Agent connects to Dashboard
+
+ ssl_certificate /data/letsencrypt/fullchain.pem;# Your domain certificate path
+ ssl_certificate_key /data/letsencrypt/key.pem;# Your domain's private key path
+
+ underscores_in_headerson;
+
+ location /{
+ grpc_read_timeout300s;
+ grpc_send_timeout300s;
+ grpc_pass grpc://localhost:5555;
+ }
+}
+
Caddy configuration files
data.example.com:443 { # The domain name where the Agent connects to Dashboard
+ reverse_proxy {
+ to localhost:5555
+ transport http {
+ versions h2c 2
+ }
+ }
+}
+
Dashboard Configuration
First login to the Dashboard and enter the admin panel, go to the settings page, fill in the CDN Bypassed Domain/IP with the domain name you configured in Nginx or Caddy, for example data.example.com, and save it.
Then open the /opt/nezha/dashboard/data/config.yaml file in the panel server and change proxygrpcport to the port that Nginx or Caddy is listening on, such as 443 as set in the previous step. Since we have SSL/TLS enabled in Nginx or Caddy, we need to set tls to true, restart the panel when you are done.
Agent Configuration
Log in to the admin panel, copy the one-click install command, and run the one-click install command on the corresponding server to reinstall the agent.
Enable Cloudflare CDN (optional)
According to Cloudflare gRPC requirements: gRPC services must listen on port 443 and must support TLS and HTTP/2. So if you need to enable CDN, you must use port 443 when configuring Nginx or Caddy reverse proxy gRPC and configure the certificate (Caddy will automatically apply and configure the certificate).
Log in to Cloudflare and select the domain you are using. Go to the Network page and turn on the gRPC switch, then go to the DNS page, find the resolution record of the domain with gRPC configuration, and turn on the orange cloud icon to enable CDN.
If you are using a CDN, please make sure that the CDN provider provides WebSocket service and that WebSocket is enabled
Confirm that you are using a reverse proxy requires special configuration of the WebSocket for the /ws and /terminal paths, you can click here to see the reverse proxy configuration
diff --git a/en_US/guide/q5.html b/en_US/guide/q5.html
index e4507eb2..3886db04 100644
--- a/en_US/guide/q5.html
+++ b/en_US/guide/q5.html
@@ -3,18 +3,18 @@
- Nezha Monitoring
+ How do I migrate my data to the new server and restore my backups? | Nezha Monitoring
-
+
-
-
+
+
The first step is to add a servers, which can be customized with names, groups, display index and notes. Servers in the same group will be displayed in groups in supported themes, and notes will only be displayed in the admin panel, no need to worry about leaking information.
Please refer to the previous article: Install Agent We recommend using one-click installation, that is, after configuring the communication domain name, click the button on the column one-click installation and copy it to the monitored servers for installation.
The flags related to the update of the Agent are: --disable-auto-update and --disable-force-update. Please refer to Customize Agent By default, the Agent is updated automatically, but when the user turns off automatic updates, the specified servers can also be selected for forced updates. This feature does not take effect when -disable-force-update is turned on.
This feature does not take effect when disable-command-execute is turned on. Both Linux and Windows are available and can be pasted using Ctrl+Shift+V. For connection failure, please refer to Real-time channel disconnection/online terminal connection failure. Note that in theWebShell function, the Agent also connects to the Domain names for public access via WebSocket, not via grpc.
Service area is a function setting area for setting up Agents to monitor external websites or servers The monitoring results can be viewed on the "Services" page in the home page
To add a new monitor, you can go to the "Services" page in the administration panel and click "Add Service Monitor".
To add a service monitor, you need to complete the following settings:
Name - Customize a name
Type - Select a monitoring type. Nezha currently supports three monitoring types: "HTTP-GET", "ICMP-Ping" and "TCP-Ping".
Target - Depending on the type you choose, the target is set in different ways
HTTP-GET: Selecting this type, you should enter a URL as the target, the URL should be added with http:// or https://If your target URL is https://, it will also monitor the SSL certificate of that URL and trigger a notification when the SSL certificate expires or changes. For example: https://example.com
ICMP-Ping: When selecting this type, you should enter a domain name or IP without a port number For example: 1.1.1.1 or example.com
TCP-Ping: When selecting this type, you should enter a domain name or IP and include the port number For example: 1.1.1.1:80 or example.com:22
Interval： Sets the time interval in seconds between each time Agent sends requests to the target
Coverage： Select a rule to determine which Agents to use to send requests to the target
Specific Servers： Use with coverage to select the Agent to be excluded from the rule
Notification Group： Select the notification method you have set up on the "Notification" page. Click here for more information
Enable Failure Notification： Select whether to receive target failure notifications as needed, default is inactive
After setting, click "Add" and you are done. Wait for a moment to go to the "Services" page on the home page to view the monitoring results
To manage existing service monitoring, you can go to the "Services" page in the administration panel Select a monitoring configuration and click the icon on the right to edit or delete it
If you don't want to show your homepage directly, you can set a access password here After setting the password, you need to enter the password to access the homepage
In the task area, you can set up scheduled tasks, periodic tasks, and multi-server batch execution tasks
Nezha monitoring supports pushing commands to the Agent for execution, so this feature is very flexible and can be used to periodically back up the server in conjunction with restic, rclone, or periodically restart a service to reset the network connection.
Go to the "Tasks" page of the admin panel and click "Add Scheduled Task" To add a scheduled task you need to make the following settings:
Name - Customize a task name
Cron Expression - Set schedule time, the Cron Expression is like:： * * * * * *sec min hour day month week, see details in CRON Expression Format For example: 0 0 3 * * * is Every day at 3 o'clock
Command - Just like writing shell/bat scripts, but line wrap is not recommended, Multiple Commands should be connected with &&/& For example, to execute a periodic reboot command, you can type reboot here
Coverage and Specific Servers - Similar to the settings on the Services page, select rules to determine which Agents need to execute scheduled tasks
Notification Group - Select the notification method you have set up on the "Notification" page. Click here for more information
Send Success Notification - When this item is activated, a message notification will be triggered when the task is successfully executed
To manage existing scheduled tasks, you can go to the "Tasks" page in the administration panel Select a task configuration and the three icons on the right, which are:
Execute Now - When clicked, the scheduled time will be ignored and the task will be executed immediately
Command not found Command not found may cause by missing PATH environment variable, for Linux Server, you may try adding source ~/.bashrc at beginning of your command or execute by absolute path.
Support use one-click script to install Dashboard and Agent services; Linux, WIndows, MacOS, OpenWRT and other mainstream systems are supported
Monitoring at any time
Support monitoring the system status of multiple servers at the same time, support monitoring the status of web pages, ports, SSL certificates; support notifications in case of failure, out of data and other status. Support multiple notification methods (Telegram, email, WeChat, etc.)
Lightweight O&M tool
Support WebSSH, support cyclic monitoring data, support setting scheduled tasks and running command on multiple servers
