From 0209708b03852000257901055026cdea11473e5d Mon Sep 17 00:00:00 2001 From: hhhkkk520 Date: Fri, 20 May 2022 15:28:51 +0000 Subject: [PATCH] deploy: a5aa54d4830b005ab8084eda2113ac3c0758c479 --- assets/en_US_guide_agent.md.8bed9873.js | 24 ------------------- assets/en_US_guide_agent.md.8bed9873.lean.js | 1 - assets/en_US_guide_agent.md.e58cc153.js | 23 ++++++++++++++++++ assets/en_US_guide_agent.md.e58cc153.lean.js | 1 + assets/en_US_guide_dashboard.md.1b96296b.js | 23 ++++++++++++++++++ .../en_US_guide_dashboard.md.1b96296b.lean.js | 1 + assets/en_US_guide_dashboard.md.c29d4037.js | 24 ------------------- .../en_US_guide_dashboard.md.c29d4037.lean.js | 1 - ...d3fa781a.js => guide_agent.md.6cfbf09e.js} | 2 +- ...ean.js => guide_agent.md.6cfbf09e.lean.js} | 0 developer/index.html | 2 +- developer/l10n.html | 2 +- developer/theme.html | 2 +- en_US/developer/index.html | 2 +- en_US/developer/l10n.html | 2 +- en_US/developer/theme.html | 2 +- en_US/guide/agent.html | 13 +++++----- en_US/guide/agentq.html | 2 +- en_US/guide/api.html | 2 +- en_US/guide/dashboard.html | 15 ++++++------ en_US/guide/dashboardq.html | 2 +- en_US/guide/loginq.html | 2 +- en_US/guide/notifications.html | 2 +- en_US/guide/q2.html | 2 +- en_US/guide/q3.html | 2 +- en_US/guide/q4.html | 2 +- en_US/guide/q5.html | 2 +- en_US/guide/servers.html | 2 +- en_US/guide/services.html | 2 +- en_US/guide/settings.html | 2 +- en_US/guide/tasks.html | 2 +- en_US/index.html | 2 +- guide/agent.html | 6 ++--- guide/agentq.html | 2 +- guide/api.html | 2 +- guide/dashboard.html | 2 +- guide/dashboardq.html | 2 +- guide/loginq.html | 2 +- guide/notifications.html | 2 +- guide/q1.html | 2 +- guide/q2.html | 2 +- guide/q3.html | 2 +- guide/q4.html | 2 +- guide/q5.html | 2 +- guide/servers.html | 2 +- guide/services.html | 2 +- guide/settings.html | 2 +- guide/tasks.html | 2 +- hashmap.json | 2 +- index.html | 2 +- 50 files changed, 102 insertions(+), 106 deletions(-) delete mode 100644 assets/en_US_guide_agent.md.8bed9873.js delete mode 100644 assets/en_US_guide_agent.md.8bed9873.lean.js create mode 100644 assets/en_US_guide_agent.md.e58cc153.js create mode 100644 assets/en_US_guide_agent.md.e58cc153.lean.js create mode 100644 assets/en_US_guide_dashboard.md.1b96296b.js create mode 100644 assets/en_US_guide_dashboard.md.1b96296b.lean.js delete mode 100644 assets/en_US_guide_dashboard.md.c29d4037.js delete mode 100644 assets/en_US_guide_dashboard.md.c29d4037.lean.js rename assets/{guide_agent.md.d3fa781a.js => guide_agent.md.6cfbf09e.js} (99%) rename assets/{guide_agent.md.d3fa781a.lean.js => guide_agent.md.6cfbf09e.lean.js} (100%) diff --git a/assets/en_US_guide_agent.md.8bed9873.js b/assets/en_US_guide_agent.md.8bed9873.js deleted file mode 100644 index 176016a0..00000000 --- a/assets/en_US_guide_agent.md.8bed9873.js +++ /dev/null @@ -1,24 +0,0 @@ -import{_ as n,c as e,o as a,d as t}from"./app.2c402e15.js";const b='{"title":"Install Agent using one-click script","description":"","frontmatter":{},"headers":[{"level":2,"title":"Install Agent using one-click script","slug":"install-agent-using-one-click-script"},{"level":3,"title":"\u51C6\u5907\u5DE5\u4F5C","slug":"\u51C6\u5907\u5DE5\u4F5C"},{"level":3,"title":"Linux\u4E00\u952E\u5B89\u88C5","slug":"linux\u4E00\u952E\u5B89\u88C5"},{"level":3,"title":"Windows\u4E00\u952E\u5B89\u88C5","slug":"windows\u4E00\u952E\u5B89\u88C5"},{"level":2,"title":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent","slug":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5agent"},{"level":3,"title":"Linux\u5B89\u88C5Agent","slug":"linux\u5B89\u88C5agent"},{"level":3,"title":"Windows\u5B89\u88C5Agent","slug":"windows\u5B89\u88C5agent"},{"level":3,"title":"OpenWRT\u5B89\u88C5Agent","slug":"openwrt\u5B89\u88C5agent"},{"level":2,"title":"\u81EA\u5B9A\u4E49Agent\u76D1\u63A7\u9879\u76EE","slug":"\u81EA\u5B9A\u4E49agent\u76D1\u63A7\u9879\u76EE"}],"relativePath":"en_US/guide/agent.md"}',s={},i=t(`

\u54EA\u5412\u76D1\u63A7\u7684\u88AB\u63A7\u7AEF\u670D\u52A1\u88AB\u79F0\u4E3AAgent\uFF0C\u672C\u6587\u6863\u5C06\u4ECB\u7ECD\u5982\u4F55\u5728\u88AB\u63A7\u7AEF\u670D\u52A1\u5668\u4E0A\u5B89\u88C5Agent\uFF0C\u5E76\u4E0EDashboard\u8FDE\u63A5

Install Agent using one-click script

\u76EE\u524D\u54EA\u5412\u76D1\u63A7\u5DF2\u652F\u6301\u5728WIndows\u548CLinux\u4E0A\u4E00\u952E\u5B89\u88C5Agent\uFF0C\u9075\u5FAA\u672C\u6587\u6863\u7684\u6B65\u9AA4\uFF0C\u4F60\u53EF\u4EE5\u5F88\u8F7B\u677E\u7684\u5728\u670D\u52A1\u5668\u4E0A\u90E8\u7F72\u5B83

\u51C6\u5907\u5DE5\u4F5C

\u4F60\u9700\u8981\u63D0\u524D\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u8BBE\u7F6E\u597D\u901A\u4FE1\u57DF\u540D\uFF0C\u6B64\u57DF\u540D\u4E0D\u53EF\u4EE5\u63A5\u5165CDN\uFF0C\u8FD9\u91CC\u4EE5\u524D\u9762\u63D0\u5230\u8FC7\u7684\u793A\u4F8B\u901A\u4FE1\u57DF\u540D \u201Cdata.example.com\u201D \u6765\u505A\u6F14\u793A
\u8FDB\u5165\u540E\u53F0\u7BA1\u7406\u9762\u677F\uFF0C\u8F6C\u5230\u201C\u8BBE\u7F6E\u201D\u9875\uFF0C\u5728\u201C\u672A\u63A5\u5165CDN\u7684\u9762\u677F\u670D\u52A1\u5668\u57DF\u540D/IP\u201D\u9879\u4E2D\u586B\u5165\u901A\u4FE1\u57DF\u540D\uFF0C\u7136\u540E\u70B9\u51FB"\u4FDD\u5B58"

Linux\u4E00\u952E\u5B89\u88C5

Windows\u4E00\u952E\u5B89\u88C5

\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent


Linux\u5B89\u88C5Agent 

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
-
-

Windows\u5B89\u88C5Agent

OpenWRT\u5B89\u88C5Agent

\u5982\u4F55\u4F7F \u65E7\u7248OpenWRT/LEDE \u81EA\u542F\u52A8

\u5982\u4F55\u4F7F \u65B0\u7248OpenWRT \u81EA\u542F\u52A8\uFF1F\u6765\u81EA @\u827E\u65AF\u5FB7\u65AF

#!/bin/sh /etc/rc.common
-
-START=99
-USE_PROCD=1
-
-start_service() {
- procd_open_instance
- procd_set_param command /root/nezha-agent -s \u9762\u677F\u901A\u4FE1\u5730\u5740:\u7AEF\u53E3 -p \u79D8\u94A5 -d
- procd_set_param respawn
- procd_close_instance
-}
-
-stop_service() {
-    killall nezha-agent
-}
-
-restart() {
- stop
- sleep 2
- start
-}
-

\u81EA\u5B9A\u4E49Agent\u76D1\u63A7\u9879\u76EE

\u81EA\u5B9A\u4E49\u76D1\u63A7\u7684\u7F51\u5361\u548C\u786C\u76D8\u5206\u533A

\u5176\u4ED6\u8FD0\u884C\u53C2\u6570

\u901A\u8FC7\u6267\u884C ./nezha-agent --help \u67E5\u770B\u652F\u6301\u7684\u53C2\u6570\uFF0C\u5982\u679C\u4F60\u4F7F\u7528\u4E86\u4E00\u952E\u811A\u672C\u5B89\u88C5Agent\uFF0C\u53EF\u4EE5\u7F16\u8F91 /etc/systemd/system/nezha-agent.service\uFF0C\u5728 ExecStart= \u8FD9\u4E00\u884C\u7684\u672B\u5C3E\u52A0\u4E0A\u4EE5\u4E0B\u53C2\u6570

`,38),l=[i];function o(r,c,p,d,h,u){return a(),e("div",null,l)}var k=n(s,[["render",o]]);export{b as __pageData,k as default}; diff --git a/assets/en_US_guide_agent.md.8bed9873.lean.js b/assets/en_US_guide_agent.md.8bed9873.lean.js deleted file mode 100644 index acca2e82..00000000 --- a/assets/en_US_guide_agent.md.8bed9873.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as n,c as e,o as a,d as t}from"./app.2c402e15.js";const b='{"title":"Install Agent using one-click script","description":"","frontmatter":{},"headers":[{"level":2,"title":"Install Agent using one-click script","slug":"install-agent-using-one-click-script"},{"level":3,"title":"\u51C6\u5907\u5DE5\u4F5C","slug":"\u51C6\u5907\u5DE5\u4F5C"},{"level":3,"title":"Linux\u4E00\u952E\u5B89\u88C5","slug":"linux\u4E00\u952E\u5B89\u88C5"},{"level":3,"title":"Windows\u4E00\u952E\u5B89\u88C5","slug":"windows\u4E00\u952E\u5B89\u88C5"},{"level":2,"title":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent","slug":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5agent"},{"level":3,"title":"Linux\u5B89\u88C5Agent","slug":"linux\u5B89\u88C5agent"},{"level":3,"title":"Windows\u5B89\u88C5Agent","slug":"windows\u5B89\u88C5agent"},{"level":3,"title":"OpenWRT\u5B89\u88C5Agent","slug":"openwrt\u5B89\u88C5agent"},{"level":2,"title":"\u81EA\u5B9A\u4E49Agent\u76D1\u63A7\u9879\u76EE","slug":"\u81EA\u5B9A\u4E49agent\u76D1\u63A7\u9879\u76EE"}],"relativePath":"en_US/guide/agent.md"}',s={},i=t("",38),l=[i];function o(r,c,p,d,h,u){return a(),e("div",null,l)}var k=n(s,[["render",o]]);export{b as __pageData,k as default}; diff --git a/assets/en_US_guide_agent.md.e58cc153.js b/assets/en_US_guide_agent.md.e58cc153.js new file mode 100644 index 00000000..6020ff64 --- /dev/null +++ b/assets/en_US_guide_agent.md.e58cc153.js @@ -0,0 +1,23 @@ +import{_ as e,c as n,o as t,d as a}from"./app.2c402e15.js";const m='{"title":"Install Agent using one-click script","description":"","frontmatter":{},"headers":[{"level":2,"title":"Install Agent using one-click script","slug":"install-agent-using-one-click-script"},{"level":3,"title":"Preparation","slug":"preparation"},{"level":3,"title":"One-click installation on Linux","slug":"one-click-installation-on-linux"},{"level":3,"title":"One-click installation on Windows","slug":"one-click-installation-on-windows"},{"level":2,"title":"Other ways to install Agent","slug":"other-ways-to-install-agent"},{"level":3,"title":"Installing Agent on Linux","slug":"installing-agent-on-linux"},{"level":3,"title":"Installing Agent on Windows","slug":"installing-agent-on-windows"},{"level":3,"title":"Installing Agent on OpenWRT","slug":"installing-agent-on-openwrt"},{"level":2,"title":"Customize Agent","slug":"customize-agent"}],"relativePath":"en_US/guide/agent.md"}',i={},o=a(`

The service in the monitored server is called Agent. This document will describe how to install the Agent on the monitored server and connect it with Dashboard

Install Agent using one-click script

Nezha Monitoring now supports one-click installation of the Agent on Windows and Linux. Follow the steps in this document and you can easily deploy it on your server

Preparation

First of all, you need to set up the communication domain name in the settings page of the admin panel, this domain name can not connect to the CDN, here is the sample communication domain name "data.example.com" mentioned earlier for demonstration
Enter the administration panel, go to the "Settings" page, in the item "CDN Bypassed Domain/IP ", fill in the communication domain name, and then click "Save"

One-click installation on Linux

One-click installation on Windows

Other ways to install Agent


Installing Agent on Linux 

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install_en.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh   
+

Installing Agent on Windows

Installing Agent on OpenWRT

How to make the old version of OpenWRT/LEDE self-boot?

How to make the new version of OpenWRT self-boot? By @\u827E\u65AF\u5FB7\u65AF

#!/bin/sh /etc/rc.common
+
+START=99
+USE_PROCD=1
+
+start_service() {
+ procd_open_instance
+ procd_set_param command /root/nezha-agent -s data.example.com:5555 -p secreat -d
+ procd_set_param respawn
+ procd_close_instance
+}
+
+stop_service() {
+    killall nezha-agent
+}
+
+restart() {
+ stop
+ sleep 2
+ start
+}
+

Customize Agent

Customize the NIC and hard drive partitions to be monitored

Other Flags

Run ./nezha-agent --help to view supported flags\uFF0Cif you are already using the one-click script, you can edit /etc/systemd/system/nezha-agent.service\uFF0Cat the end of this line ExecStart= add:

`,30),s=[o];function l(r,c,d,p,h,u){return t(),n("div",null,s)}var f=e(i,[["render",l]]);export{m as __pageData,f as default}; diff --git a/assets/en_US_guide_agent.md.e58cc153.lean.js b/assets/en_US_guide_agent.md.e58cc153.lean.js new file mode 100644 index 00000000..8f69a5f1 --- /dev/null +++ b/assets/en_US_guide_agent.md.e58cc153.lean.js @@ -0,0 +1 @@ +import{_ as e,c as n,o as t,d as a}from"./app.2c402e15.js";const m='{"title":"Install Agent using one-click script","description":"","frontmatter":{},"headers":[{"level":2,"title":"Install Agent using one-click script","slug":"install-agent-using-one-click-script"},{"level":3,"title":"Preparation","slug":"preparation"},{"level":3,"title":"One-click installation on Linux","slug":"one-click-installation-on-linux"},{"level":3,"title":"One-click installation on Windows","slug":"one-click-installation-on-windows"},{"level":2,"title":"Other ways to install Agent","slug":"other-ways-to-install-agent"},{"level":3,"title":"Installing Agent on Linux","slug":"installing-agent-on-linux"},{"level":3,"title":"Installing Agent on Windows","slug":"installing-agent-on-windows"},{"level":3,"title":"Installing Agent on OpenWRT","slug":"installing-agent-on-openwrt"},{"level":2,"title":"Customize Agent","slug":"customize-agent"}],"relativePath":"en_US/guide/agent.md"}',i={},o=a("",30),s=[o];function l(r,c,d,p,h,u){return t(),n("div",null,s)}var f=e(i,[["render",l]]);export{m as __pageData,f as default}; diff --git a/assets/en_US_guide_dashboard.md.1b96296b.js b/assets/en_US_guide_dashboard.md.1b96296b.js new file mode 100644 index 00000000..0a2b5b31 --- /dev/null +++ b/assets/en_US_guide_dashboard.md.1b96296b.js @@ -0,0 +1,23 @@ +import{_ as e,c as t,o as a,d as n}from"./app.2c402e15.js";const b='{"title":"Preparations","description":"","frontmatter":{},"headers":[{"level":2,"title":"Preparations","slug":"preparations"},{"level":2,"title":"Get the Client ID and Client Secret on Github","slug":"get-the-client-id-and-client-secret-on-github"},{"level":2,"title":"Installing Dashboard on the server","slug":"installing-dashboard-on-the-server"},{"level":2,"title":"Configure reverse proxy","slug":"configure-reverse-proxy"},{"level":2,"title":"Configuring SSL in the aaPanel","slug":"configuring-ssl-in-the-aapanel"}],"relativePath":"en_US/guide/dashboard.md"}',o={},s=n(`

Preparations

To setup a Nezha monitorning Dashboard, you need these things:

  1. A VPS that can connect to the Internet, firewall and security policies need to open ports 8008 and 5555, otherwise it will be inaccessible and unable to receive data. A 1 core 512MB RAM server is sufficient for most usage scenarios
  2. A domain name that has been set up with an A record that resolves to the Dashboard server IP

TIP

If you want to use CDN, please prepare two domains, one connect to CDN for public access, CDN needs to support WebSocket protocol; the other domain should not connect to CDN, use it as Agent to send data to Dashboard.
This document uses "cdn.example.com" and "data.example.com" domains to demonstrate respectively

  1. A Github account

This document will use the aaPanel as an example, with future versions of the changes, some of the features may change, this document is for reference only

Get the Client ID and Client Secret on Github

Nezha Monitor uses a Github account as the login account for the admin panel

Installing Dashboard on the server 

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install_en.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
+
./nezha.sh
+

to open the management script


Configure reverse proxy 

#PROXY-START/
+location / {
+    proxy_pass http://127.0.0.1:8008;
+    proxy_set_header Host $host;
+    proxy_set_header      Upgrade $http_upgrade;
+}
+location ~ ^/(ws|terminal/.+)$  {
+    proxy_pass http://127.0.0.1:8008;
+    proxy_http_version 1.1;
+    proxy_set_header Upgrade $http_upgrade;
+    proxy_set_header Connection "Upgrade";
+    proxy_set_header Host $host;
+}
+#PROXY-END/
+

Other:



Configuring SSL in the aaPanel

First, temporarily disable the reverse proxy
As with other websites, you can choose to automatically apply for a Let\xB4s 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

`,25),r=[s];function i(l,c,p,h,u,d){return a(),t("div",null,r)}var m=e(o,[["render",i]]);export{b as __pageData,m as default}; diff --git a/assets/en_US_guide_dashboard.md.1b96296b.lean.js b/assets/en_US_guide_dashboard.md.1b96296b.lean.js new file mode 100644 index 00000000..c1f80841 --- /dev/null +++ b/assets/en_US_guide_dashboard.md.1b96296b.lean.js @@ -0,0 +1 @@ +import{_ as e,c as t,o as a,d as n}from"./app.2c402e15.js";const b='{"title":"Preparations","description":"","frontmatter":{},"headers":[{"level":2,"title":"Preparations","slug":"preparations"},{"level":2,"title":"Get the Client ID and Client Secret on Github","slug":"get-the-client-id-and-client-secret-on-github"},{"level":2,"title":"Installing Dashboard on the server","slug":"installing-dashboard-on-the-server"},{"level":2,"title":"Configure reverse proxy","slug":"configure-reverse-proxy"},{"level":2,"title":"Configuring SSL in the aaPanel","slug":"configuring-ssl-in-the-aapanel"}],"relativePath":"en_US/guide/dashboard.md"}',o={},s=n("",25),r=[s];function i(l,c,p,h,u,d){return a(),t("div",null,r)}var m=e(o,[["render",i]]);export{b as __pageData,m as default}; diff --git a/assets/en_US_guide_dashboard.md.c29d4037.js b/assets/en_US_guide_dashboard.md.c29d4037.js deleted file mode 100644 index 7108fb20..00000000 --- a/assets/en_US_guide_dashboard.md.c29d4037.js +++ /dev/null @@ -1,24 +0,0 @@ -import{_ as e,c as a,o as n,d as t}from"./app.2c402e15.js";const k='{"title":"Preparations","description":"","frontmatter":{},"headers":[{"level":3,"title":"Preparations","slug":"preparations"},{"level":3,"title":"\u83B7\u53D6Github\u7684Client ID\u548C\u5BC6\u94A5","slug":"\u83B7\u53D6github\u7684client-id\u548C\u5BC6\u94A5"},{"level":3,"title":"\u5728\u670D\u52A1\u5668\u4E2D\u5B89\u88C5Dashboard","slug":"\u5728\u670D\u52A1\u5668\u4E2D\u5B89\u88C5dashboard"},{"level":3,"title":"\u914D\u7F6E\u53CD\u5411\u4EE3\u7406","slug":"\u914D\u7F6E\u53CD\u5411\u4EE3\u7406"},{"level":3,"title":"\u5728\u5B9D\u5854\u9762\u677F\u4E2D\u914D\u7F6ESSL","slug":"\u5728\u5B9D\u5854\u9762\u677F\u4E2D\u914D\u7F6Essl"}],"relativePath":"en_US/guide/dashboard.md"}',s={},o=t(`

Preparations

\u642D\u5EFA\u4E00\u4E2A\u54EA\u5412\u76D1\u63A7\uFF0C\u4F60\u9700\u8981\uFF1A

  1. \u4E00\u53F0\u53EF\u4EE5\u8FDE\u63A5\u516C\u7F51\u7684VPS\uFF0C\u9632\u706B\u5899\u548C\u5B89\u5168\u7B56\u7565\u9700\u8981\u653E\u884C8008\u548C5555\u7AEF\u53E3\uFF0C\u5426\u5219\u4F1A\u65E0\u6CD5\u8BBF\u95EE\u548C\u65E0\u6CD5\u63A5\u6536\u6570\u636E\u3002\u5355\u6838512MB\u5185\u5B58\u7684\u670D\u52A1\u5668\u914D\u7F6E\u5C31\u8DB3\u4EE5\u6EE1\u8DB3\u5927\u591A\u6570\u4F7F\u7528\u573A\u666F
  2. \u4E00\u4E2A\u5DF2\u7ECF\u8BBE\u7F6E\u597DA\u8BB0\u5F55\uFF0C\u6307\u5411Dashboard\u670D\u52A1\u5668ip\u7684\u57DF\u540D

TIP

\u5982\u679C\u4F60\u60F3\u4F7F\u7528CDN\uFF0C\u8BF7\u51C6\u5907\u4E24\u4E2A\u57DF\u540D\uFF0C\u4E00\u4E2A\u914D\u7F6E\u597DCDN\u7528\u4F5C\u516C\u5F00\u8BBF\u95EE\uFF0CCDN\u9700\u8981\u652F\u6301WebSocket\u534F\u8BAE\uFF1B\u53E6\u4E00\u4E2A\u57DF\u540D\u4E0D\u8981\u4F7F\u7528CDN\uFF0C\u7528\u4F5CAgent\u7AEF\u4E0EDashboard\u7684\u901A\u4FE1
\u672C\u6587\u6863\u5206\u522B\u4EE5 "cdn.example.com" \u548C "data.example.com" \u4E24\u4E2A\u57DF\u540D\u6765\u6F14\u793A

  1. \u4E00\u4E2AGithub/Gitee\u8D26\u53F7

\u672C\u6587\u6863\u5C06\u4EE5\u5B9D\u5854\u9762\u677F\u53CD\u4EE3\u9762\u677F\u7684\u8FC7\u7A0B\u4F5C\u4E3A\u8303\u4F8B\uFF0C\u968F\u7740\u672A\u6765\u7248\u672C\u7684\u53D8\u5316\uFF0C\u90E8\u5206\u529F\u80FD\u7684\u5165\u53E3\u53EF\u80FD\u4F1A\u53D1\u751F\u6539\u53D8\uFF0C\u672C\u6587\u6863\u4EC5\u4F9B\u53C2\u8003

\u83B7\u53D6Github\u7684Client ID\u548C\u5BC6\u94A5

\u54EA\u5412\u76D1\u63A7\u63A5\u5165Github\u548CGitee\u4F5C\u4E3A\u540E\u53F0\u7BA1\u7406\u5458\u8D26\u53F7

\u5728\u670D\u52A1\u5668\u4E2D\u5B89\u88C5Dashboard 

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
-

\u5982\u679C\u4F60\u7684\u9762\u677F\u670D\u52A1\u5668\u4F4D\u4E8E\u4E2D\u56FD\u5927\u9646\uFF0C\u53EF\u4EE5\u4F7F\u7528\u955C\u50CF\uFF1A

curl -L https://fastly.jsdelivr.net/gh/naiba/nezha@master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh
-
./nezha.sh
-

\u6765\u6253\u5F00\u7BA1\u7406\u811A\u672C


\u914D\u7F6E\u53CD\u5411\u4EE3\u7406 

#PROXY-START/
-location / {
-    proxy_pass http://127.0.0.1:8008;
-    proxy_set_header Host $host;
-    proxy_set_header      Upgrade $http_upgrade;
-}
-location ~ ^/(ws|terminal/.+)$  {
-    proxy_pass http://127.0.0.1:8008;
-    proxy_http_version 1.1;
-    proxy_set_header Upgrade $http_upgrade;
-    proxy_set_header Connection "Upgrade";
-    proxy_set_header Host $host;
-}
-#PROXY-END/
-

\u6269\u5C55\u5185\u5BB9\uFF1A



\u5728\u5B9D\u5854\u9762\u677F\u4E2D\u914D\u7F6ESSL

\u9996\u5148\uFF0C\u5148\u6682\u65F6\u5173\u95ED\u53CD\u5411\u4EE3\u7406
\u6B63\u5982\u5728\u5176\u4ED6\u7F51\u7AD9\u4E2D\u914D\u7F6ESSL\u8BC1\u4E66\u4E00\u6837\uFF0C\u8FDB\u5165\u7AD9\u70B9\u8BBE\u7F6E\u4E2D\u7684\u201CSSL\u201D\uFF0C\u4F60\u53EF\u4EE5\u9009\u62E9\u81EA\u52A8\u7533\u8BF7 Let\xB4s Encrypt \u8BC1\u4E66\u6216\u624B\u52A8\u914D\u7F6E\u5DF2\u6709\u7684\u8BC1\u4E66
\u5B8C\u6210SSL\u7684\u8BBE\u7F6E\u540E\uFF0C\u4F60\u9700\u8981\u56DE\u5230 https://github.com/settings/developers \uFF0C\u7F16\u8F91\u4E4B\u524D\u521B\u5EFA\u7684\u9A8C\u8BC1\u5E94\u7528\u7A0B\u5E8F\uFF0C\u5C06\u4E4B\u524D\u6211\u4EEC\u586B\u5165\u7684"Homepage URL"\u548C"Authorization callback URL"\u4E2D\u7684\u57DF\u540D\u5168\u90E8\u4ECEhttp\u6539\u4E3Ahttps\uFF0C\u5982\uFF1A"https://cdn.example.com" \u548C "https://cdn.example.com/oauth2/callback" \uFF0C\u4E0D\u66F4\u6539\u6B64\u9879\u53EF\u80FD\u4F1A\u5BFC\u81F4\u4F60\u65E0\u6CD5\u767B\u9646\u9762\u677F\u540E\u53F0

`,32),r=[o];function p(l,c,i,d,h,u){return n(),a("div",null,r)}var m=e(s,[["render",p]]);export{k as __pageData,m as default}; diff --git a/assets/en_US_guide_dashboard.md.c29d4037.lean.js b/assets/en_US_guide_dashboard.md.c29d4037.lean.js deleted file mode 100644 index 82196071..00000000 --- a/assets/en_US_guide_dashboard.md.c29d4037.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as n,d as t}from"./app.2c402e15.js";const k='{"title":"Preparations","description":"","frontmatter":{},"headers":[{"level":3,"title":"Preparations","slug":"preparations"},{"level":3,"title":"\u83B7\u53D6Github\u7684Client ID\u548C\u5BC6\u94A5","slug":"\u83B7\u53D6github\u7684client-id\u548C\u5BC6\u94A5"},{"level":3,"title":"\u5728\u670D\u52A1\u5668\u4E2D\u5B89\u88C5Dashboard","slug":"\u5728\u670D\u52A1\u5668\u4E2D\u5B89\u88C5dashboard"},{"level":3,"title":"\u914D\u7F6E\u53CD\u5411\u4EE3\u7406","slug":"\u914D\u7F6E\u53CD\u5411\u4EE3\u7406"},{"level":3,"title":"\u5728\u5B9D\u5854\u9762\u677F\u4E2D\u914D\u7F6ESSL","slug":"\u5728\u5B9D\u5854\u9762\u677F\u4E2D\u914D\u7F6Essl"}],"relativePath":"en_US/guide/dashboard.md"}',s={},o=t("",32),r=[o];function p(l,c,i,d,h,u){return n(),a("div",null,r)}var m=e(s,[["render",p]]);export{k as __pageData,m as default}; diff --git a/assets/guide_agent.md.d3fa781a.js b/assets/guide_agent.md.6cfbf09e.js similarity index 99% rename from assets/guide_agent.md.d3fa781a.js rename to assets/guide_agent.md.6cfbf09e.js index a7e24e23..d65f8018 100644 --- a/assets/guide_agent.md.d3fa781a.js +++ b/assets/guide_agent.md.6cfbf09e.js @@ -1,4 +1,4 @@ -import{_ as n,c as e,o as a,d as t}from"./app.2c402e15.js";const b='{"title":"\u4E00\u952E\u5B89\u88C5Agent","description":"","frontmatter":{},"headers":[{"level":2,"title":"\u4E00\u952E\u5B89\u88C5Agent","slug":"\u4E00\u952E\u5B89\u88C5agent"},{"level":3,"title":"\u51C6\u5907\u5DE5\u4F5C","slug":"\u51C6\u5907\u5DE5\u4F5C"},{"level":3,"title":"Linux\u4E00\u952E\u5B89\u88C5","slug":"linux\u4E00\u952E\u5B89\u88C5"},{"level":3,"title":"Windows\u4E00\u952E\u5B89\u88C5","slug":"windows\u4E00\u952E\u5B89\u88C5"},{"level":2,"title":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent","slug":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5agent"},{"level":3,"title":"Linux\u5B89\u88C5Agent","slug":"linux\u5B89\u88C5agent"},{"level":3,"title":"Windows\u5B89\u88C5Agent","slug":"windows\u5B89\u88C5agent"},{"level":3,"title":"OpenWRT\u5B89\u88C5Agent","slug":"openwrt\u5B89\u88C5agent"},{"level":2,"title":"\u81EA\u5B9A\u4E49Agent\u76D1\u63A7\u9879\u76EE","slug":"\u81EA\u5B9A\u4E49agent\u76D1\u63A7\u9879\u76EE"}],"relativePath":"guide/agent.md"}',s={},o=t(`

\u54EA\u5412\u76D1\u63A7\u7684\u88AB\u63A7\u7AEF\u670D\u52A1\u88AB\u79F0\u4E3AAgent\uFF0C\u672C\u6587\u6863\u5C06\u4ECB\u7ECD\u5982\u4F55\u5728\u88AB\u63A7\u7AEF\u670D\u52A1\u5668\u4E0A\u5B89\u88C5Agent\uFF0C\u5E76\u4E0EDashboard\u8FDE\u63A5

\u4E00\u952E\u5B89\u88C5Agent

\u76EE\u524D\u54EA\u5412\u76D1\u63A7\u5DF2\u652F\u6301\u5728WIndows\u548CLinux\u4E0A\u4E00\u952E\u5B89\u88C5Agent\uFF0C\u9075\u5FAA\u672C\u6587\u6863\u7684\u6B65\u9AA4\uFF0C\u4F60\u53EF\u4EE5\u5F88\u8F7B\u677E\u7684\u5728\u670D\u52A1\u5668\u4E0A\u90E8\u7F72\u5B83

\u51C6\u5907\u5DE5\u4F5C

\u4F60\u9700\u8981\u63D0\u524D\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u8BBE\u7F6E\u597D\u901A\u4FE1\u57DF\u540D\uFF0C\u6B64\u57DF\u540D\u4E0D\u53EF\u4EE5\u63A5\u5165CDN\uFF0C\u8FD9\u91CC\u4EE5\u524D\u9762\u63D0\u5230\u8FC7\u7684\u793A\u4F8B\u901A\u4FE1\u57DF\u540D \u201Cdata.example.com\u201D \u6765\u505A\u6F14\u793A
\u8FDB\u5165\u540E\u53F0\u7BA1\u7406\u9762\u677F\uFF0C\u8F6C\u5230\u201C\u8BBE\u7F6E\u201D\u9875\uFF0C\u5728\u201C\u672A\u63A5\u5165CDN\u7684\u9762\u677F\u670D\u52A1\u5668\u57DF\u540D/IP\u201D\u9879\u4E2D\u586B\u5165\u901A\u4FE1\u57DF\u540D\uFF0C\u7136\u540E\u70B9\u51FB"\u4FDD\u5B58"

Linux\u4E00\u952E\u5B89\u88C5

Windows\u4E00\u952E\u5B89\u88C5

\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent

Linux\u5B89\u88C5Agent 

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
+import{_ as n,c as e,o as a,d as t}from"./app.2c402e15.js";const b='{"title":"\u4E00\u952E\u5B89\u88C5Agent","description":"","frontmatter":{},"headers":[{"level":2,"title":"\u4E00\u952E\u5B89\u88C5Agent","slug":"\u4E00\u952E\u5B89\u88C5agent"},{"level":3,"title":"\u51C6\u5907\u5DE5\u4F5C","slug":"\u51C6\u5907\u5DE5\u4F5C"},{"level":3,"title":"Linux\u4E00\u952E\u5B89\u88C5","slug":"linux\u4E00\u952E\u5B89\u88C5"},{"level":3,"title":"Windows\u4E00\u952E\u5B89\u88C5","slug":"windows\u4E00\u952E\u5B89\u88C5"},{"level":2,"title":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent","slug":"\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5agent"},{"level":3,"title":"Linux\u5B89\u88C5Agent","slug":"linux\u5B89\u88C5agent"},{"level":3,"title":"Windows\u5B89\u88C5Agent","slug":"windows\u5B89\u88C5agent"},{"level":3,"title":"OpenWRT\u5B89\u88C5Agent","slug":"openwrt\u5B89\u88C5agent"},{"level":2,"title":"\u81EA\u5B9A\u4E49Agent\u76D1\u63A7\u9879\u76EE","slug":"\u81EA\u5B9A\u4E49agent\u76D1\u63A7\u9879\u76EE"}],"relativePath":"guide/agent.md"}',s={},o=t(`
\u54EA\u5412\u76D1\u63A7\u7684\u88AB\u63A7\u7AEF\u670D\u52A1\u88AB\u79F0\u4E3AAgent\uFF0C\u672C\u6587\u6863\u5C06\u4ECB\u7ECD\u5982\u4F55\u5728\u88AB\u63A7\u7AEF\u670D\u52A1\u5668\u4E0A\u5B89\u88C5Agent\uFF0C\u5E76\u4E0EDashboard\u8FDE\u63A5

\u4E00\u952E\u5B89\u88C5Agent 
\u76EE\u524D\u54EA\u5412\u76D1\u63A7\u5DF2\u652F\u6301\u5728Windows\u548CLinux\u4E0A\u4E00\u952E\u5B89\u88C5Agent\uFF0C\u9075\u5FAA\u672C\u6587\u6863\u7684\u6B65\u9AA4\uFF0C\u4F60\u53EF\u4EE5\u5F88\u8F7B\u677E\u7684\u5728\u670D\u52A1\u5668\u4E0A\u90E8\u7F72\u5B83

\u51C6\u5907\u5DE5\u4F5C 
\u4F60\u9700\u8981\u63D0\u524D\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u8BBE\u7F6E\u597D\u901A\u4FE1\u57DF\u540D\uFF0C\u6B64\u57DF\u540D\u4E0D\u53EF\u4EE5\u63A5\u5165CDN\uFF0C\u8FD9\u91CC\u4EE5\u524D\u9762\u63D0\u5230\u8FC7\u7684\u793A\u4F8B\u901A\u4FE1\u57DF\u540D \u201Cdata.example.com\u201D \u6765\u505A\u6F14\u793A
 \u8FDB\u5165\u540E\u53F0\u7BA1\u7406\u9762\u677F\uFF0C\u8F6C\u5230\u201C\u8BBE\u7F6E\u201D\u9875\uFF0C\u5728\u201C\u672A\u63A5\u5165CDN\u7684\u9762\u677F\u670D\u52A1\u5668\u57DF\u540D/IP\u201D\u9879\u4E2D\u586B\u5165\u901A\u4FE1\u57DF\u540D\uFF0C\u7136\u540E\u70B9\u51FB"\u4FDD\u5B58"

Linux\u4E00\u952E\u5B89\u88C5 
  • \u9996\u5148\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u6DFB\u52A0\u4E00\u53F0\u670D\u52A1\u5668
  • \u70B9\u51FB\u65B0\u6DFB\u52A0\u7684\u670D\u52A1\u5668\u65C1\uFF0C\u7EFF\u8272\u7684Linux\u56FE\u6807\u6309\u94AE\uFF0C\u590D\u5236\u4E00\u952E\u5B89\u88C5\u547D\u4EE4
  • \u5728\u88AB\u63A7\u7AEF\u670D\u52A1\u5668\u4E2D\u8FD0\u884C\u590D\u5236\u7684\u4E00\u952E\u5B89\u88C5\u547D\u4EE4\uFF0C\u7B49\u5F85\u5B89\u88C5\u5B8C\u6210\u540E\u8FD4\u56DE\u5230Dashboard\u4E3B\u9875\u67E5\u770B\u670D\u52A1\u5668\u662F\u5426\u4E0A\u7EBF

Windows\u4E00\u952E\u5B89\u88C5 
  • \u9996\u5148\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u6DFB\u52A0\u4E00\u53F0\u670D\u52A1\u5668
  • \u70B9\u51FB\u65B0\u6DFB\u52A0\u7684\u670D\u52A1\u5668\u65C1\uFF0C\u7EFF\u8272\u7684Windows\u56FE\u6807\u6309\u94AE\uFF0C\u590D\u5236\u4E00\u952E\u5B89\u88C5\u547D\u4EE4
  • \u8FDB\u5165Windows\u670D\u52A1\u5668\uFF0C\u8FD0\u884CPowerShell\uFF0C\u5728PowerShell\u4E2D\u8FD0\u884C\u590D\u5236\u7684\u5B89\u88C5\u547D\u4EE4
  • \u5982\u9047\u5230\u786E\u8BA4\u300C\u6267\u884C\u7B56\u7565\u53D8\u66F4\u300D\u8BF7\u9009\u62E9 Y
  • \u7B49\u5F85\u5B89\u88C5\u5B8C\u6210\u540E\u8FD4\u56DEDashboard\u4E3B\u9875\u67E5\u770B\u670D\u52A1\u5668\u662F\u5426\u4E0A\u7EBF



\u5176\u4ED6\u65B9\u5F0F\u5B89\u88C5Agent 
Linux\u5B89\u88C5Agent 
  • \u9996\u5148\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u6DFB\u52A0\u4E00\u53F0\u670D\u52A1\u5668
  • \u5728\u88AB\u63A7\u670D\u52A1\u5668\u4E2D\uFF0C\u8FD0\u884C\u811A\u672C\uFF08\u4F4D\u4E8E\u4E2D\u56FD\u5927\u9646\u7684\u670D\u52A1\u5668\u8BF7\u4F7F\u7528\u955C\u50CF\uFF09\uFF1A
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
 
\u5982\u679C\u4F60\u7684\u88AB\u63A7\u670D\u52A1\u5668\u4F4D\u4E8E\u4E2D\u56FD\u5927\u9646\uFF0C\u53EF\u4EE5\u4F7F\u7528\u955C\u50CF\uFF1A
curl -L https://fastly.jsdelivr.net/gh/naiba/nezha@master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh
 
  • \u9009\u62E9\u201C\u5B89\u88C5\u76D1\u63A7Agent\u201D
  • \u8F93\u5165\u901A\u4FE1\u57DF\u540D\uFF0C\u5982\uFF1A\u201Ddata.example.com\u201C
  • \u8F93\u5165\u9762\u677F\u901A\u4FE1\u7AEF\u53E3\uFF08RPC\u7AEF\u53E3\uFF09\uFF0C\u9ED8\u8BA4\u4E3A5555
  • \u8F93\u5165Agent\u5BC6\u94A5\uFF0CAgent\u5BC6\u94A5\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u6DFB\u52A0\u670D\u52A1\u5668\u65F6\u751F\u6210\uFF0C\u53EF\u4EE5\u5728\u7BA1\u7406\u9762\u677F\u4E2D\u7684\u201C\u4E3B\u673A\u201D\u9875\u4E2D\u627E\u5230
  • \u7B49\u5F85\u5B89\u88C5\u5B8C\u6210\u540E\u8FD4\u56DEDashboard\u4E3B\u9875\u67E5\u770B\u670D\u52A1\u5668\u662F\u5426\u4E0A\u7EBF

Windows\u5B89\u88C5Agent 
OpenWRT\u5B89\u88C5Agent 
\u5982\u4F55\u4F7F \u65E7\u7248OpenWRT/LEDE \u81EA\u542F\u52A8
\u5982\u4F55\u4F7F \u65B0\u7248OpenWRT \u81EA\u542F\u52A8\uFF1F\u6765\u81EA @\u827E\u65AF\u5FB7\u65AF
  • \u9996\u5148\u5728 release \u4E0B\u8F7D\u5BF9\u5E94\u7684\u4E8C\u8FDB\u5236\u89E3\u538B zip \u5305\u540E\u653E\u7F6E\u5230 /root
  • \u8FD0\u884C chmod +x /root/nezha-agent \u8D4B\u4E88\u6267\u884C\u6743\u9650\uFF0C\u7136\u540E\u521B\u5EFA /etc/init.d/nezha-service\uFF1A
#!/bin/sh /etc/rc.common
 
diff --git a/assets/guide_agent.md.d3fa781a.lean.js b/assets/guide_agent.md.6cfbf09e.lean.js
similarity index 100%
rename from assets/guide_agent.md.d3fa781a.lean.js
rename to assets/guide_agent.md.6cfbf09e.lean.js
diff --git a/developer/index.html b/developer/index.html
index fe11a2b8..f41c6081 100644
--- a/developer/index.html
+++ b/developer/index.html
@@ -14,7 +14,7 @@
   
   
     
 哪吒监控
开发手册
欢迎使用哪吒监控开发手册，我们欢迎你提出高质量的Pull Request，帮助哪吒监控变得更好！
开始使用 → 
Copyright © 2022-present Nezhahq

-    
+    
     
     
   
diff --git a/developer/l10n.html b/developer/l10n.html
index efd314a5..67d226ac 100644
--- a/developer/l10n.html
+++ b/developer/l10n.html
@@ -14,7 +14,7 @@
   
   
     
 哪吒监控
哪吒监控的Dashboard已经添加本地化，支持多个语言，你可以在开发新功能时遵循以下步骤来支持本地化
WARNING
哪吒监控使用 Crowdin 平台翻译文本，请不要直接修改除 zh-CN.toml 以外的toml文件
使用说明 
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中的配置来替换新功能中的文本
  2. 如果新功能中有新的文本，请将新文本拉取到 zh-CN.toml 中
  3. 在Pull Request被合并后，你可以前往 Crowdin 平台贡献新文本的翻译

-    
+    
     
     
   
diff --git a/developer/theme.html b/developer/theme.html
index 60d5acd4..a862291d 100644
--- a/developer/theme.html
+++ b/developer/theme.html
@@ -14,7 +14,7 @@
   
   
     
 哪吒监控
哪吒主题开发环境 
哪吒面板提供了主题开发环境，你可以使用它来创建新的哪吒监控主题
WARNING
请注意： 此开发环境仅支持 dashboard v0.13.16 及更新版本。
使用说明 
  1. 克隆此仓库到本地
  2. 修改 data/config.yaml 中的oauth2 配置（回调连接可以填 http://localhost 的）
  3. docker-compose up
  4. 开始开发
  5. 主题制作完成之后可以将 theme-custom 放置到服务器上的 /opt/nezha/dashboard/theme-custom 位置
FAQ 
  • 如果不能使用 80 端口，在 docker-compose.yaml 中修改配置。

-    
+    
     
     
   
diff --git a/en_US/developer/index.html b/en_US/developer/index.html
index dbdb5f58..dce5e666 100644
--- a/en_US/developer/index.html
+++ b/en_US/developer/index.html
@@ -14,7 +14,7 @@
   
   
     
 Nezha Monitoring
Development Manual
Welcome to the Nezha Monitoring Development Manual.
Start Now → 
Copyright © 2022-present Nezhahq

-    
+    
     
     
   
diff --git a/en_US/developer/l10n.html b/en_US/developer/l10n.html
index 240398d2..401a27e7 100644
--- a/en_US/developer/l10n.html
+++ b/en_US/developer/l10n.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/developer/theme.html b/en_US/developer/theme.html
index 4ff6fc97..8f76108e 100644
--- a/en_US/developer/theme.html
+++ b/en_US/developer/theme.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/agent.html b/en_US/guide/agent.html
index bbbc053b..473c8f8c 100644
--- a/en_US/guide/agent.html
+++ b/en_US/guide/agent.html
@@ -7,22 +7,21 @@
     
     
     
-    
+    
     
     
   
   
   
-    
 Nezha Monitoring
哪吒监控的被控端服务被称为Agent，本文档将介绍如何在被控端服务器上安装Agent，并与Dashboard连接

Install Agent using one-click script 
目前哪吒监控已支持在WIndows和Linux上一键安装Agent，遵循本文档的步骤，你可以很轻松的在服务器上部署它

准备工作 
你需要提前在管理面板中设置好通信域名，此域名不可以接入CDN，这里以前面提到过的示例通信域名 “data.example.com” 来做演示
 进入后台管理面板，转到“设置”页，在“未接入CDN的面板服务器域名/IP”项中填入通信域名，然后点击"保存"

Linux一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Linux图标按钮，复制一键安装命令
  • 在被控端服务器中运行复制的一键安装命令，等待安装完成后返回到Dashboard主页查看服务器是否上线

Windows一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Windows图标按钮，复制一键安装命令
  • 进入Windows服务器，运行PowerShell，在PowerShell中运行复制的安装命令
  • 如遇到确认「执行策略变更」请选择 Y
  • 等待安装完成后返回Dashboard主页查看服务器是否上线



其他方式安装Agent 

Linux安装Agent 
  • 首先在管理面板中添加一台服务器
  • 在被控服务器中，运行脚本（位于中国大陆的服务器请使用镜像）：
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
-
-
  • 选择“安装监控Agent”
  • 输入通信域名，如：”data.example.com“
  • 输入面板通信端口，默认为5555
  • 输入Agent密钥，Agent密钥在管理面板中添加服务器时生成，可以在管理面板中的“主机”页中找到
  • 等待安装完成后返回Dashboard主页查看服务器是否上线

Windows安装Agent 
OpenWRT安装Agent 
如何使 旧版OpenWRT/LEDE 自启动
如何使 新版OpenWRT 自启动？来自 @艾斯德斯
  • 首先在 release 下载对应的二进制解压 zip 包后放置到 /root
  • 运行 chmod +x /root/nezha-agent 赋予执行权限，然后创建 /etc/init.d/nezha-service：
#!/bin/sh /etc/rc.common
+    
 Nezha Monitoring
The service in the monitored server is called Agent. This document will describe how to install the Agent on the monitored server and connect it with Dashboard

Install Agent using one-click script 
Nezha Monitoring now supports one-click installation of the Agent on Windows and Linux. Follow the steps in this document and you can easily deploy it on your server

Preparation 
First of all, you need to set up the communication domain name in the settings page of the admin panel, this domain name can not connect to the CDN, here is the sample communication domain name "data.example.com" mentioned earlier for demonstration
 Enter the administration panel, go to the "Settings" page, in the item "CDN Bypassed Domain/IP ", fill in the communication domain name, and then click "Save"

One-click installation on Linux 
  • First add a server in the admin panel
  • Click on the green Linux icon button next to the newly added server and copy the one-click installation command
  • Run the copied one-click installation command on the monitored server, wait for the installation to complete, and then return to the Dashboard home page to see if the server is online.

One-click installation on Windows 
  • First add a server in the admin panel
  • Click on the green Linux icon button next to the newly added server and copy the one-click installation command
  • Login to Windows Server, open PowerShell, and run the copied installation command in PowerShell
  • If you encounter the prompt "Implement Policy Change" please select Y
  • Wait for the installation to complete and return to the Dashboard home page to see if the server is online



Other ways to install Agent 

Installing Agent on Linux 
  • First add a server in the admin panel
  • In the monitored server, run the script:
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install_en.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh   
+
  • Select “Install_agent”
  • Input the communication domain name, e.g. "data.example.com"
  • Input RPC port, default is 5555
  • Input the Agent Secret, which is generated when adding a server in the administration panel and can be found in the " Servers " page of the administration panel
  • Wait for the installation to complete and return to the Dashboard home page to see if the server is online

Installing Agent on Windows 
Installing Agent on OpenWRT 
How to make the old version of OpenWRT/LEDE self-boot?
How to make the new version of OpenWRT self-boot? By @艾斯德斯
  • First download the corresponding binary from the release, unzip the zip package and place it in /root
  • Then run chmod +x /root/nezha-agent to give it execute access, create file /etc/init.d/nezha-service：
#!/bin/sh /etc/rc.common
 
 START=99
 USE_PROCD=1
 
 start_service() {
  procd_open_instance
- procd_set_param command /root/nezha-agent -s 面板通信地址:端口 -p 秘钥 -d
+ procd_set_param command /root/nezha-agent -s data.example.com:5555 -p secreat -d
  procd_set_param respawn
  procd_close_instance
 }
@@ -36,8 +35,8 @@
  sleep 2
  start
 }
-
  • 运行 chmod +x /etc/init.d/nezha-service 赋予执行权限
  • 启动服务： /etc/init.d/nezha-service enable && /etc/init.d/nezha-service start



自定义Agent监控项目 
自定义监控的网卡和硬盘分区 
  • 执行 /opt/nezha/agent/nezha-agent --edit-agent-config 来选择自定义的网卡和分区，然后重启 Agent 即可生效
其他运行参数 
通过执行 ./nezha-agent --help 查看支持的参数，如果你使用了一键脚本安装Agent，可以编辑 /etc/systemd/system/nezha-agent.service，在 ExecStart= 这一行的末尾加上以下参数
  • --report-delay 控制系统信息上报的间隔，默认为 1 秒，可以设置为 3 来进一步降低 agent 端系统资源占用（配置区间 1-4）
  • --skip-conn 不监控连接数，推荐 机场/连接密集型服务器或CPU占用较高的服务器设置
  • --skip-procs 不监控进程数，也可以降低 agent 占用
  • --disable-auto-update 禁止 自动更新 Agent（安全特性）
  • --disable-force-update 禁止 强制更新 Agent（安全特性）
  • --disable-command-execute 禁止在 Agent 上执行定时任务、打开在线终端（安全特性）
  • --tls 启用 SSL/TLS 加密（使用 nginx 反向代理 Agent 的 grpc 连接，并且 nginx 开启 SSL/TLS 时，需要启用该项配置）

-    
+
  • Give it permission to execute: chmod +x /etc/init.d/nezha-service
  • Start the service /etc/init.d/nezha-service enable && /etc/init.d/nezha-service start

Customize Agent 
Customize the NIC and hard drive partitions to be monitored 
  • Run /opt/nezha/agent/nezha-agent --edit-agent-config to select a custom NIC and partition, and then restart Agent
Other Flags 
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-auto-update Disable Automatic Update Agent (security feature)
  • --disable-force-update Disable Forced Update Agent (security feature)
  • --disable-command-execute Disable execution of scheduled tasks, disallow open online terminals on the Agent side (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)

+    
     
     
   
diff --git a/en_US/guide/agentq.html b/en_US/guide/agentq.html
index 9d7c99df..9f986fad 100644
--- a/en_US/guide/agentq.html
+++ b/en_US/guide/agentq.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/api.html b/en_US/guide/api.html
index 6edecc96..571df355 100644
--- a/en_US/guide/api.html
+++ b/en_US/guide/api.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/dashboard.html b/en_US/guide/dashboard.html
index 1573ae01..2d994351 100644
--- a/en_US/guide/dashboard.html
+++ b/en_US/guide/dashboard.html
@@ -7,16 +7,15 @@
     
     
     
-    
+    
     
     
   
   
   
-    
 Nezha Monitoring
Preparations 
搭建一个哪吒监控，你需要：
  1. 一台可以连接公网的VPS，防火墙和安全策略需要放行8008和5555端口，否则会无法访问和无法接收数据。单核512MB内存的服务器配置就足以满足大多数使用场景
  2. 一个已经设置好A记录，指向Dashboard服务器ip的域名
TIP
如果你想使用CDN，请准备两个域名，一个配置好CDN用作公开访问，CDN需要支持WebSocket协议；另一个域名不要使用CDN，用作Agent端与Dashboard的通信
 本文档分别以 "cdn.example.com" 和 "data.example.com" 两个域名来演示
  1. 一个Github/Gitee账号
本文档将以宝塔面板反代面板的过程作为范例，随着未来版本的变化，部分功能的入口可能会发生改变，本文档仅供参考

获取Github的Client ID和密钥 
哪吒监控接入Github和Gitee作为后台管理员账号
  • 首先我们需要新建一个验证应用，以Github为例，登陆Github后，打开 https://github.com/settings/developers ，依次选择“OAuth Apps” - “New OAuth App”
    Application name - 随意填写
    Homepage URL - 填写面板的访问域名，如："http://cdn.example.com"
    Authorization callback URL - 填写回调地址，如："http://cdn.example.com/oauth2/callback"
  • 点击“Register application”
  • 保存页面中的Client ID，然后点击 “Generate a new client secret“，创建一个新的Client Secret，新建的密钥仅会显示一次，请妥善保存 

在服务器中安装Dashboard 
  • 在面板服务器中，运行安装脚本：
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
-
如果你的面板服务器位于中国大陆，可以使用镜像：
curl -L https://fastly.jsdelivr.net/gh/naiba/nezha@master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh
-
  • 等待Docker安装完毕后，分别输入以下值：
    OAuth提供商 - Github或Gitee
    Client ID - 之前保存的Client ID
    Client Secret - 之前保存的密钥
    用户名 - Github或Gitee的用户名
    站点标题 - 自定义站点标题
    访问端口 - 公开访问端口，可自定义，默认8008
    Agent的通信端口 - Agent与Dashboard的通信端口，默认5555
  • 输入完成后，等待拉取镜像
     安装结束后，如果一切正常，此时你可以访问域名+端口号，如 “http://cdn.example.com:8008” 来查看面板
  • 将来如果需要再次运行脚本，可以运行：
./nezha.sh
-
来打开管理脚本


配置反向代理 
  • 在宝塔面板中新建一个站点，域名填写公开访问域名，如 “http://cdn.example.com“ ，然后点击“设置”进入站点设置选项，选择“反向代理” - “新建反向代理”
  • 自定义一个代理名称，在下方“目标URL”中填入 http://127.0.0.1 然后点击“保存”
  • 打开刚刚新建的反向代理右边的“配置文件”，将配置文件替换为以下内容：
#PROXY-START/
+    
 Nezha Monitoring
Preparations 
To setup a Nezha monitorning Dashboard, you need these things:
  1. A VPS that can connect to the Internet, firewall and security policies need to open ports 8008 and 5555, otherwise it will be inaccessible and unable to receive data. A 1 core 512MB RAM server is sufficient for most usage scenarios
  2. A domain name that has been set up with an A record that resolves to the Dashboard server IP
TIP
If you want to use CDN, please prepare two domains, one connect to CDN for public access, CDN needs to support WebSocket protocol; the other domain should not connect to CDN, use it as Agent to send data to Dashboard.
 This document uses "cdn.example.com" and "data.example.com" domains to demonstrate respectively
  1. A Github account
This document will use the aaPanel as an example, with future versions of the changes, some of the features may change, this document is for reference only

Get the Client ID and Client Secret on Github 
Nezha Monitor uses a Github account as the login account for the admin panel
  • First we need to create a new authentication application, after logging into Github, open https://github.com/settings/developers and select "OAuth Apps" - "New OAuth App "
    Application name - Fill in as you like
    Homepage URL - Fill in the panel's access domain name, such as: "http://cdn.example.com"
    Authorization callback URL - Fill in the callback address, e.g., "http://cdn.example.com/oauth2/callback"
  • Click on "Registration Application"
  • Remember the Client ID in the page, then click "Generate a new client secret" to create a new Client Secret, the new secret will be displayed only once, please save it properly 

Installing Dashboard on the server 
  • In the panel server, run the installation script:
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install_en.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
+
  • After waiting for the Docker installation to complete, input the following settings:
    OAuth2 provider - Github
    Client ID - Previously saved Client ID
    Client Secret - Previously saved secret
    GitHub/Gitee login name - Github username
    Site title - Custom site title
    Site access port - Public access port, customizable, default 8008
    RPC port - The communication port between Agent and Dashboard, default 5555
  • After the input is complete, wait to pull the mirror
     After the installation, if everything is fine, you can visit the domain + port number, such as "http://cdn.example.com:8008" to view the Dashboard
  • In the future, if you need to run the script again, you can run:
./nezha.sh
+
to open the management script


Configure reverse proxy 
  • Create a new site in the aaPanel, fill in the public access domain name, such as "http://cdn.example.com", then click "Settings" to enter the site settings option, select " Reverse proxy" - "New reverse proxy"
  • Customize a proxy name, fill in http://127.0.0.1 in the "Target URL" and click "Save"
  • Open the " configuration" to the right of the new reverse proxy you just created and replace the configuration file with the following:
#PROXY-START/
 location / {
     proxy_pass http://127.0.0.1:8008;
     proxy_set_header Host $host;
@@ -30,14 +29,14 @@
     proxy_set_header Host $host;
 }
 #PROXY-END/
-
  • 点击“保存”
     现在，你应该可以直接使用域名，如：“http://cdn.example.com“ 来访问面板了

扩展内容： 
  • CaddyServer v1（v2 无需特别配置）
    proxy /ws http://ip:8008 {
+
    • Click "Save"
       Now, you should be able to access the panel directly using a domain name such as: "http://cdn.example.com"

    Other: 
    • CaddyServer v1（v2 no special configuration required）
      proxy /ws http://ip:8008 {
     websocket
 }
 proxy /terminal/* http://ip:8008 {
     websocket
 }
-


    在宝塔面板中配置SSL 
    首先，先暂时关闭反向代理
     正如在其他网站中配置SSL证书一样，进入站点设置中的“SSL”，你可以选择自动申请 Let´s Encrypt 证书或手动配置已有的证书
     完成SSL的设置后，你需要回到 https://github.com/settings/developers ，编辑之前创建的验证应用程序，将之前我们填入的"Homepage URL"和"Authorization callback URL"中的域名全部从http改为https，如："https://cdn.example.com" 和 "https://cdn.example.com/oauth2/callback" ，不更改此项可能会导致你无法登陆面板后台

-    
+


Configuring SSL in the aaPanel 
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

+    
     
     
   
diff --git a/en_US/guide/dashboardq.html b/en_US/guide/dashboardq.html
index 0312eaf1..0a282d5a 100644
--- a/en_US/guide/dashboardq.html
+++ b/en_US/guide/dashboardq.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/loginq.html b/en_US/guide/loginq.html
index 483f0fd8..4bde35d3 100644
--- a/en_US/guide/loginq.html
+++ b/en_US/guide/loginq.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/notifications.html b/en_US/guide/notifications.html
index d57a242f..6da1583f 100644
--- a/en_US/guide/notifications.html
+++ b/en_US/guide/notifications.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/q2.html b/en_US/guide/q2.html
index 0ae3d3f1..cd8ba10d 100644
--- a/en_US/guide/q2.html
+++ b/en_US/guide/q2.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/q3.html b/en_US/guide/q3.html
index b0d6fdd0..d63ff49c 100644
--- a/en_US/guide/q3.html
+++ b/en_US/guide/q3.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/q4.html b/en_US/guide/q4.html
index 05e3a4ec..94a71278 100644
--- a/en_US/guide/q4.html
+++ b/en_US/guide/q4.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/q5.html b/en_US/guide/q5.html
index 745b783c..cb4b5b64 100644
--- a/en_US/guide/q5.html
+++ b/en_US/guide/q5.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/servers.html b/en_US/guide/servers.html
index caa7d149..11f2cabe 100644
--- a/en_US/guide/servers.html
+++ b/en_US/guide/servers.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/services.html b/en_US/guide/services.html
index 53d8e385..5223ac6d 100644
--- a/en_US/guide/services.html
+++ b/en_US/guide/services.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/settings.html b/en_US/guide/settings.html
index 10c286dd..b802f62e 100644
--- a/en_US/guide/settings.html
+++ b/en_US/guide/settings.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/guide/tasks.html b/en_US/guide/tasks.html
index e23422f2..d0d017b1 100644
--- a/en_US/guide/tasks.html
+++ b/en_US/guide/tasks.html
@@ -14,7 +14,7 @@
   
   
     
-    
+    
     
     
   
diff --git a/en_US/index.html b/en_US/index.html
index d81c11b2..1bd14c97 100644
--- a/en_US/index.html
+++ b/en_US/index.html
@@ -14,7 +14,7 @@
   
   
     
 Nezha Monitoring
Nezha Monitoring
A open source, lightweight server and website monitoring and O&M tool
Learn More → 
One-Click Installation
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
Copyright © 2022-present Nezhahq

-    
+    
     
     
   
diff --git a/guide/agent.html b/guide/agent.html
index 3eea940b..9ae4f20d 100644
--- a/guide/agent.html
+++ b/guide/agent.html
@@ -7,13 +7,13 @@
     
     
     
-    
+    
     
     
   
   
   
-    
 哪吒监控
哪吒监控的被控端服务被称为Agent，本文档将介绍如何在被控端服务器上安装Agent，并与Dashboard连接

一键安装Agent 
目前哪吒监控已支持在WIndows和Linux上一键安装Agent，遵循本文档的步骤，你可以很轻松的在服务器上部署它

准备工作 
你需要提前在管理面板中设置好通信域名，此域名不可以接入CDN，这里以前面提到过的示例通信域名 “data.example.com” 来做演示
 进入后台管理面板，转到“设置”页，在“未接入CDN的面板服务器域名/IP”项中填入通信域名，然后点击"保存"

Linux一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Linux图标按钮，复制一键安装命令
  • 在被控端服务器中运行复制的一键安装命令，等待安装完成后返回到Dashboard主页查看服务器是否上线

Windows一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Windows图标按钮，复制一键安装命令
  • 进入Windows服务器，运行PowerShell，在PowerShell中运行复制的安装命令
  • 如遇到确认「执行策略变更」请选择 Y
  • 等待安装完成后返回Dashboard主页查看服务器是否上线



其他方式安装Agent 
Linux安装Agent 
  • 首先在管理面板中添加一台服务器
  • 在被控服务器中，运行脚本（位于中国大陆的服务器请使用镜像）：
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
+    
 哪吒监控
哪吒监控的被控端服务被称为Agent，本文档将介绍如何在被控端服务器上安装Agent，并与Dashboard连接

一键安装Agent 
目前哪吒监控已支持在Windows和Linux上一键安装Agent，遵循本文档的步骤，你可以很轻松的在服务器上部署它

准备工作 
你需要提前在管理面板中设置好通信域名，此域名不可以接入CDN，这里以前面提到过的示例通信域名 “data.example.com” 来做演示
 进入后台管理面板，转到“设置”页，在“未接入CDN的面板服务器域名/IP”项中填入通信域名，然后点击"保存"

Linux一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Linux图标按钮，复制一键安装命令
  • 在被控端服务器中运行复制的一键安装命令，等待安装完成后返回到Dashboard主页查看服务器是否上线

Windows一键安装 
  • 首先在管理面板中添加一台服务器
  • 点击新添加的服务器旁，绿色的Windows图标按钮，复制一键安装命令
  • 进入Windows服务器，运行PowerShell，在PowerShell中运行复制的安装命令
  • 如遇到确认「执行策略变更」请选择 Y
  • 等待安装完成后返回Dashboard主页查看服务器是否上线



其他方式安装Agent 
Linux安装Agent 
  • 首先在管理面板中添加一台服务器
  • 在被控服务器中，运行脚本（位于中国大陆的服务器请使用镜像）：
curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh
 
如果你的被控服务器位于中国大陆，可以使用镜像：
curl -L https://fastly.jsdelivr.net/gh/naiba/nezha@master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh
 
  • 选择“安装监控Agent”
  • 输入通信域名，如：”data.example.com“
  • 输入面板通信端口（RPC端口），默认为5555
  • 输入Agent密钥，Agent密钥在管理面板中添加服务器时生成，可以在管理面板中的“主机”页中找到
  • 等待安装完成后返回Dashboard主页查看服务器是否上线

Windows安装Agent 
OpenWRT安装Agent 
如何使 旧版OpenWRT/LEDE 自启动
如何使 新版OpenWRT 自启动？来自 @艾斯德斯
  • 首先在 release 下载对应的二进制解压 zip 包后放置到 /root
  • 运行 chmod +x /root/nezha-agent 赋予执行权限，然后创建 /etc/init.d/nezha-service：
#!/bin/sh /etc/rc.common
 
@@ -37,7 +37,7 @@
  start
 }
 
  • 运行 chmod +x /etc/init.d/nezha-service 赋予执行权限
  • 启动服务： /etc/init.d/nezha-service enable && /etc/init.d/nezha-service start



自定义Agent监控项目 
自定义监控的网卡和硬盘分区 
  • 执行 /opt/nezha/agent/nezha-agent --edit-agent-config 来选择自定义的网卡和分区，然后重启 Agent 即可生效
其他运行参数 
通过执行 ./nezha-agent --help 查看支持的参数，如果你使用了一键脚本安装Agent，可以编辑 /etc/systemd/system/nezha-agent.service，在 ExecStart= 这一行的末尾加上以下参数
  • --report-delay 控制系统信息上报的间隔，默认为 1 秒，可以设置为 3 来进一步降低 agent 端系统资源占用（配置区间 1-4）
  • --skip-conn 不监控连接数，推荐 机场/连接密集型服务器或CPU占用较高的服务器设置
  • --skip-procs 不监控进程数，也可以降低 agent 占用
  • --disable-auto-update 禁止 自动更新 Agent（安全特性）
  • --disable-force-update 禁止 强制更新 Agent（安全特性）
  • --disable-command-execute 禁止在 Agent 上执行定时任务、打开在线终端（安全特性）
  • --tls 启用 SSL/TLS 加密（使用 nginx 反向代理 Agent 的 grpc 连接，并且 nginx 开启 SSL/TLS 时，需要启用该项配置）

-    
+    
     
     
   
diff --git a/guide/agentq.html b/guide/agentq.html
index 60954937..70ce24dc 100644
--- a/guide/agentq.html
+++ b/guide/agentq.html
@@ -14,7 +14,7 @@
   
   
     
 哪吒监控
Agent相关 
后台显示的IP和Agent实际IP不一致？ 
请查看Dashboard相关-后台显示的IP和Agent实际IP不一致？
 在此不再赘述。
一键脚本安装出错 
curl: Failed to connect to raw.githubusercontent.com...... 
多出现在国内主机中，目前一键脚本只从github直接获取安装脚本，您可以多尝试几次，或者手动安装Agent，别忘了使用镜像。

-    
+    
     
     
   
diff --git a/guide/api.html b/guide/api.html
index ab876940..c454d71d 100644
--- a/guide/api.html
+++ b/guide/api.html
@@ -126,7 +126,7 @@ Authorization: Token
     ]
 }
 

-    
+    
     
     
   
diff --git a/guide/dashboard.html b/guide/dashboard.html
index 651a9f17..27693634 100644
--- a/guide/dashboard.html
+++ b/guide/dashboard.html
@@ -37,7 +37,7 @@ proxy /terminal/* http://ip:8008 {
     websocket
 }
 


在宝塔面板中配置SSL 
首先，先暂时关闭反向代理
 正如在其他网站中配置SSL证书一样，进入站点设置中的“SSL”，你可以选择自动申请 Let´s Encrypt 证书或手动配置已有的证书
 完成SSL的设置后，你需要回到 https://github.com/settings/developers ，编辑之前创建的验证应用程序，将之前我们填入的"Homepage URL"和"Authorization callback URL"中的域名全部从http改为https，如："https://cdn.example.com" 和 "https://cdn.example.com/oauth2/callback" ，不更改此项可能会导致你无法登陆面板后台
- + diff --git a/guide/dashboardq.html b/guide/dashboardq.html index 32c642da..9baca3fc 100644 --- a/guide/dashboardq.html +++ b/guide/dashboardq.html @@ -17,7 +17,7 @@ curl ip.sb curl ip-api.com

查看密码忘记\删除查看密码

请查看或编辑/opt/nezha/dashboard/data/config.yaml文件。
密码位于site-viewpassword。

- + diff --git a/guide/loginq.html b/guide/loginq.html index 17f95dcd..f750e16b 100644 --- a/guide/loginq.html +++ b/guide/loginq.html @@ -14,7 +14,7 @@
哪吒监控

登陆相关

- + diff --git a/guide/notifications.html b/guide/notifications.html index 6c88f1e1..4cf4fae2 100644 --- a/guide/notifications.html +++ b/guide/notifications.html @@ -14,7 +14,7 @@
哪吒监控

哪吒监控支持对服务器的负载、CPU、内存、硬盘、带宽、流量、月流量、进程数、连接数进行监控，并在其中某项达到用户设定值时发送报警通知

灵活的通知方式

#NEZHA# 是面板消息占位符，面板触发通知时会自动用实际消息替换占位符

Body 内容是JSON 格式的：当请求类型为 FORM 时，值为 key:value 的形式，value 里面可放置占位符，通知时会自动替换。当请求类型为 JSON 时 只会简单进行字符串替换后直接提交到URL。

URL 里面也可放置占位符，请求时会进行简单的字符串替换。

你可以参考以下的通知方式示例，也可以根据自己的需求灵活设置推送方式

  • server酱示例

  • wxpusher 示例，需要关注你的应用

  • Telegram 示例 @haitau 贡献

    • 名称：telegram 机器人消息通知
    • URL：https://api.telegram.org/botXXXXXX/sendMessage?chat_id=YYYYYY&text=#NEZHA#
    • 请求方式: GET
    • 请求类型: 默认
    • Body: 空
    • URL 参数获取说明：botXXXXXX 中的 XXXXXX 是在 telegram 中关注官方 @Botfather ，输入/newbot ，创建新的机器人（bot）时，会提供的 token（在提示 Use this token to access the HTTP API:后面一行）这里 'bot' 三个字母不可少。创建 bot 后，需要先在 telegram 中与 BOT 进行对话（随便发个消息），然后才可用 API 发送消息。YYYYYY 是 telegram 用户的数字 ID。与机器人@userinfobot 对话可获得。


报警规则说明

基本规则

  • type：可选取一个或多个类型，如在一个规则中选择了多个类型，需要同时满足所有选择的类型才会触发通知（可参考后面的示例）
    • cpu、memory、swap、disk
    • net_in_speed 入站网速、net_out_speed 出站网速、net_all_speed 双向网速、transfer_in 入站流量、transfer_out 出站流量、transfer_all 双向流量
    • offline 离线监控
    • load1、load5、load15 负载
    • process_count 进程数 目前取线程数占用资源太多，暂时不支持
    • tcp_conn_count、udp_conn_count 连接数
  • duration：持续数秒，数秒内采样记录 30% 以上触发阈值才会报警（防数据插针）
  • min 或 max：
    • 流量、网速类数值 为字节（1KB=1024B，1MB = 1024*1024B）
    • 内存、硬盘、CPU 以占用百分比计数
    • 离线监控无需设置此项
  • cover：
    • 0 监控所有，通过 ignore 忽略特定服务器
    • 1 忽略所有，通过 ignore 监控特定服务器
      例如：[{"type":"offline","duration":10, "cover":0, "ignore":{"5": true}}]
  • ignore: 选择忽略特定服务器，搭配 cover 使用，内容为服务器id和布尔值，例如：{"1": true, "2":false}

完整示例:

TIP

添加一个离线报警

  • 名称：离线通知
  • 规则：[{"Type":"offline","Duration":10}]
  • 启用：√

TIP

添加一个监控 CPU 持续 10s 超过 50% 且 内存持续 20s 占用低于 20% 的报警

  • 名称：CPU+内存
  • 规则：[{"Type":"cpu","Min":0,"Max":50,"Duration":10},{"Type":"memory","Min":20,"Max":0,"Duration":20}]
  • 启用：√

特殊：任意周期流量报警

可以用作月流量报警

  • type:
    • transfer_in_cycle 周期内的入站流量
    • transfer_out_cycle 周期内的出站流量
    • transfer_all_cycle 周期内双向流量和
  • cycle_start： 统计周期开始日期（可以是你机器计费周期的开始日期），时间格式为RFC3339，例如北京时间为2022-01-11T08:00:00.00+08:00
  • cycle_interval：每隔多少个周期单位（例如，周期单位为天，该值为 7，则代表每隔 7 天统计一次）
  • cycle_unit 统计周期单位，默认hour,可选(hour, day, week, month, year)
  • min/max、cover、ignore 参考基本规则配置

示例: ID 为 3 的服务器（ignore 里面定义），以每月 15 号为统计周期，周期内统计的出站月流量达到 1TB 时报警 [{"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/guide/q1.html b/guide/q1.html index 91368087..b43d0b80 100644 --- a/guide/q1.html +++ b/guide/q1.html @@ -60,7 +60,7 @@ ufw allow proto tcp from serverIp to any port 443443 -j DROP iptables -I INPUT -s serverIp -p tcp --dport 443 -j ACCEPT
- + diff --git a/guide/q2.html b/guide/q2.html index dfe6df57..15e64dba 100644 --- a/guide/q2.html +++ b/guide/q2.html @@ -14,7 +14,7 @@
哪吒监控

Agent 启动/上线 问题自检流程

  1. 直接执行 /opt/nezha/agent/nezha-agent -s 面板IP或非CDN域名:面板RPC端口 -p Agent密钥 -d 查看日志是否是因为 DNS、网络不佳导致超时（timeout）
  2. nc -v 域名/IP 面板RPC端口 或者 telnet 域名/IP 面板RPC端口 来检验是否是网络问题，检查本机与面板服务器的出入站防火墙，如果无法判断问题可借助 https://port.ping.pe/ 提供的端口检查工具进行检测。
  3. 如果上面步骤检测正常，Agent 正常上线，尝试关闭 SELinux，如何关闭 SELinux？
- + diff --git a/guide/q3.html b/guide/q3.html index c60875ad..1e94ce42 100644 --- a/guide/q3.html +++ b/guide/q3.html @@ -38,7 +38,7 @@ } }

Dashboard 面板端配置

Agent 端配置

开启 Cloudflare CDN（可选）

根据 Cloudflare gRPC 的要求：gRPC 服务必须侦听 443 端口 且必须支持 TLS 和 HTTP/2。 所以如果需要开启 CDN，必须在配置 Nginx 或者 Caddy 反向代理 gRPC 时使用 443 端口，并配置证书（Caddy 会自动申请并配置证书）。

- + diff --git a/guide/q4.html b/guide/q4.html index 8922136d..13368193 100644 --- a/guide/q4.html +++ b/guide/q4.html @@ -14,7 +14,7 @@
哪吒监控

实时通道断开/在线终端连接失败

  • 如果你使用了CDN，请确认CDN服务商提供WebSocket服务，并且已开启WebSocket
  • 确认你的反代规则中针对 /ws,/terminal 路径的 WebSocket 进行了特别配置，你可以 点击这里 查看反向代理配置
- + diff --git a/guide/q5.html b/guide/q5.html index 49b55252..97a1f3cb 100644 --- a/guide/q5.html +++ b/guide/q5.html @@ -14,7 +14,7 @@
哪吒监控

如何进行数据迁移、备份恢复？

  1. 先运行一键脚本，选择 停止面板
  2. 在旧服务器中打包 /opt/nezha 文件夹，复制到新环境相同位置解压
  3. 在新环境中运行一键脚本，选择 启动面板
- + diff --git a/guide/servers.html b/guide/servers.html index 5ae8e262..521648e2 100644 --- a/guide/servers.html +++ b/guide/servers.html @@ -14,7 +14,7 @@
哪吒监控

主机

介绍

主机区域负责管理Agent，是哪吒探针中最基础的区域，也是其他功能的基础。

添加服务器

第一步是添加主机，可以自定义名称、分组、排序和备注。
拥有相同分组的主机会在受支持的主题中划分到一起进行显示，备注仅会在后台显示，无需担心泄露信息。

安装Agent

请参考前文安装Agent
推荐使用一键安装，即配置好参数后，点击主机一键安装列上的按钮，复制到相应主机进行安装。

强制更新

强制更新对应的是自定义agent监控项目中的--disable-auto-update和--disable-force-update。
默认情况下，Agent会自动更新，无需干预。但当用户关闭自动更新后，也可以选中指定主机进行强制更新。
disable-force-update开启时此功能不生效。

数据列

  • 版本号: 记录Agent当前版本
  • 密钥: 即secret\key，配置Agent时会用到
  • 一键安装: 较为便捷的Agent安装方式
  • 管理: 左为WebShell，中为编辑，右为删除

在线终端

即WebShell，disable-command-execute开启时此功能不生效。
Linux和Windows均可用，可使用Ctrl+Shift+V粘贴。
连接失败请参考实时通道断开/在线终端连接失败。
注意在线终端功能中，Agent也是通过WebSocket连接到用户使用域名，而非通过grpc交互。

- + diff --git a/guide/services.html b/guide/services.html index 3baad434..cc584215 100644 --- a/guide/services.html +++ b/guide/services.html @@ -14,7 +14,7 @@
哪吒监控

服务区域是设置 Agent 监控外部网站或服务器的功能设置区
设置好的服务监控可以在主页中的 “服务” 页查看监控结果

使用方法

如需新增一个监控，可以进入管理面板中的 “服务” 页，点击“添加监控”

新增一个服务监控，你需要设置以下参数：

  • 名称 - 自定义一个名称

  • 类型 - 选择一个监控类型，目前哪吒监控支持三种监控类型，分别是 “HTTP-GET”、“ICMP-Ping” 和 “TCP-Ping”

  • 目标 - 根据你选择的类型不同，目标的设置方法也不同

  • HTTP-GET: 选择此类型，你应该输入一个URL作为目标，URL需添加 http:// 或 https:// 如果你的目标URL是 https:// ,将会同时监控该URL的SSL证书，当SSL证书到期或发生变更，会触发提醒
    例如： https://example.com
  • ICMP-Ping: 选择此类型时，你应该输入一个域名或IP，不含端口号
    例如：1.1.1.1 或 example.com
  • TCP-Ping: 选择此类型时，你应该输入一个域名或IP并包含端口号
    例如：1.1.1.1:80 或 example.com:22

  • 请求间隔： 设定 Agent 每次请求目标的时间间隔，以秒为单位

  • 覆盖范围： 选择一条规则来确定要使用哪些 Agent 来请求目标

  • 特定服务器： 配合覆盖范围使用，选择规则内需要排除的 Agent

  • 通知方式组： 选择你已经在 “报警” 页设置好的通知方式，点击这里了解详情

  • 启用故障通知： 根据需要选择是否接收目标故障通知，默认为不勾选

设置完成后，点击 “添加” 即可
稍等片刻前往主页的 “服务” 页，查看监控结果

管理监控

如需对已有的服务监控进行管理，可以前往管理面板中的 “服务” 页
选择一条监控配置，点击右侧的图标进行编辑或删除

- + diff --git a/guide/settings.html b/guide/settings.html index 33910a25..5c08bb42 100644 --- a/guide/settings.html +++ b/guide/settings.html @@ -57,7 +57,7 @@ avatar.style} </style>

前台查看密码

如果你不想直接展示你的主页，你可以在这里设置一个查看密码
设置密码后，需要输入密码才可以访问主页

未接入CDN的面板服务器域名/IP

此项设置是使用一键脚本安装 Agent 的前提，详情请查看这里

IP 变更提醒

如果你希望当某个服务器的ip发生变更时收到通知，可以在这里进行设置

覆盖范围

在这里选择一条规则，来确定需要监控哪些服务器，可以根据自己的需求进行选择

特定服务器

配合覆盖范围的设置，在这里设置选定规则的排除项

提醒发送至指定的通知分组

选择通知方式，通知方式请提前在 “报警” 页内设置

WARNING

设置完成后，勾选启用时，通知生效


WARNING

IP变更通知默认打码，如果你不希望打码，可以勾选 “通知信息IP不打码”

- + diff --git a/guide/tasks.html b/guide/tasks.html index 7d93e459..ee7d0c3a 100644 --- a/guide/tasks.html +++ b/guide/tasks.html @@ -14,7 +14,7 @@
哪吒监控

在任务区域中，可以设置计划任务，定期任务，多服务器批量执行任务

哪吒监控支持推送命令到 Agent 执行，因此此功能非常灵活，使用此功能可以定期结合 restic、rclone 给服务器备份，或者定期重启某项服务来重置网络连接

使用方法

进入管理面板的 “任务” 页，点击 “添加计划任务”
添加计划任务你需要填入以下参数：

  • 名称 - 自定义一个任务名称

  • 计划 - 设置计划时间，时间的格式为： * * * * * * 分别对应 秒 分 时 天 月 星期，详情见计划表达式格式
    如：0 0 3 * * * 对应为 每天3点

  • 命令 - 你可以在这里设置需要执行的命令，就像写 Shell/Bat 脚本一样，但是不推荐换行，多个命令使用 &&/& 连接
    例如执行定期重启命令，可以在这里输入 reboot

  • 覆盖范围 和 特定服务器 - 跟“服务”页中的设置类似，选择规则来确定哪些 Agent 执行计划任务

  • 通知方式组 - 选择你已经在 “报警” 页设置好的通知方式，点击这里了解详情

  • 推送成功的消息 - 勾选此项，任务执行成功后会触发消息通知

管理任务

如需对已有的计划任务进行管理，可以前往管理面板中的 “任务” 页
选择一条任务配置，右侧的三个图标，分别是：

  • 立即执行 - 点击后将忽略计划时间，立刻执行任务
  • 编辑 - 点击可以修改任务配置
  • 删除 - 删除这条计划任务

常见问题

  1. xxx 命令找不到
    如果运行失败，提示 xxx 命令找不到，可能是 PATH 环境变量的问题，Linux 服务器在命令开头加入 source ~/.bashrc 或者使用绝对路径执行
- + diff --git a/hashmap.json b/hashmap.json index b22be25f..8d9823aa 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"developer_index.md":"ee592849","developer_l10n.md":"ba294ec8","developer_theme.md":"f7e1f379","en_us_developer_index.md":"b71cc532","en_us_developer_l10n.md":"7251e389","en_us_developer_theme.md":"096ab5ad","en_us_guide_agent.md":"8bed9873","en_us_guide_agentq.md":"fc681108","en_us_guide_api.md":"1cb185fb","en_us_guide_dashboard.md":"c29d4037","en_us_guide_dashboardq.md":"12f00603","en_us_guide_loginq.md":"fccba1cc","en_us_guide_notifications.md":"b30d610e","en_us_guide_q2.md":"d1c860d2","en_us_guide_q3.md":"4782ed4a","en_us_guide_q4.md":"21280a24","en_us_guide_q5.md":"410e46a9","en_us_guide_servers.md":"c9b36fe3","en_us_guide_services.md":"facaeeed","en_us_guide_settings.md":"aac5fc45","en_us_guide_tasks.md":"c5036e0b","en_us_index.md":"c8719a21","guide_agent.md":"d3fa781a","guide_agentq.md":"8f3e39d8","guide_api.md":"eb31daa7","guide_dashboard.md":"a8a51b7a","guide_dashboardq.md":"84fd553d","guide_loginq.md":"d018cda9","guide_notifications.md":"ac3a804b","guide_q1.md":"60864821","guide_q2.md":"9519d1ef","guide_q3.md":"278a14da","guide_q4.md":"49995c8a","guide_q5.md":"ef18e2c9","guide_servers.md":"aa5468b1","guide_services.md":"c286c180","guide_settings.md":"978f81fd","guide_tasks.md":"fac6c260","index.md":"2c78f74e"} +{"developer_index.md":"ee592849","developer_l10n.md":"ba294ec8","developer_theme.md":"f7e1f379","en_us_developer_index.md":"b71cc532","en_us_developer_l10n.md":"7251e389","en_us_developer_theme.md":"096ab5ad","en_us_guide_agent.md":"e58cc153","en_us_guide_agentq.md":"fc681108","en_us_guide_api.md":"1cb185fb","en_us_guide_dashboard.md":"1b96296b","en_us_guide_dashboardq.md":"12f00603","en_us_guide_loginq.md":"fccba1cc","en_us_guide_notifications.md":"b30d610e","en_us_guide_q2.md":"d1c860d2","en_us_guide_q3.md":"4782ed4a","en_us_guide_q4.md":"21280a24","en_us_guide_q5.md":"410e46a9","en_us_guide_servers.md":"c9b36fe3","en_us_guide_services.md":"facaeeed","en_us_guide_settings.md":"aac5fc45","en_us_guide_tasks.md":"c5036e0b","en_us_index.md":"c8719a21","guide_agent.md":"6cfbf09e","guide_agentq.md":"8f3e39d8","guide_api.md":"eb31daa7","guide_dashboard.md":"a8a51b7a","guide_dashboardq.md":"84fd553d","guide_loginq.md":"d018cda9","guide_notifications.md":"ac3a804b","guide_q1.md":"60864821","guide_q2.md":"9519d1ef","guide_q3.md":"278a14da","guide_q4.md":"49995c8a","guide_q5.md":"ef18e2c9","guide_servers.md":"aa5468b1","guide_services.md":"c286c180","guide_settings.md":"978f81fd","guide_tasks.md":"fac6c260","index.md":"2c78f74e"} diff --git a/index.html b/index.html index 38c2da50..7027f210 100644 --- a/index.html +++ b/index.html @@ -14,7 +14,7 @@
哪吒监控

哪吒监控

一个开源、轻量的服务器和网站监控、运维工具

开始使用 →

一键安装

支持一键脚本安装面板和监控服务，轻松使用；Linux、WIndows、MacOS、OpenWRT等主流系统均受支持

随时监控

支持同时监控多个服务器的系统状态，支持监控网页、端口、SSL证书状态；支持故障、流量等状态报警，支持多种通知方式（Telegram、邮件、微信等）

轻量运维

支持在线SSH，支持流量循环监控，支持设置定时任务、服务器批量执行任务

Copyright © 2022-present Nezhahq

- +