From bbd57a50b11e42d85b84f63275a09401fea19803 Mon Sep 17 00:00:00 2001
From: Kris <krishoodbyair@gmail.com>
Date: Tue, 14 May 2024 02:11:36 +0200
Subject: [PATCH] =?UTF-8?q?=E4=BC=98=E5=8C=96=E6=9B=B4=E6=96=B0=E4=B8=AD?=
 =?UTF-8?q?=E8=8B=B1=E6=96=87=E6=96=87=E6=A1=A3-=E7=AE=A1=E7=90=86?=
 =?UTF-8?q?=E9=9D=A2=E6=9D=BF-=E6=9C=8D=E5=8A=A1?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/en_US/guide/services.md | 66 +++++++++++++++++++-----------------
 docs/guide/services.md       | 58 +++++++++++++------------------
 2 files changed, 59 insertions(+), 65 deletions(-)

diff --git a/docs/en_US/guide/services.md b/docs/en_US/guide/services.md
index 32d56356..d0405268 100644
--- a/docs/en_US/guide/services.md
+++ b/docs/en_US/guide/services.md
@@ -1,47 +1,51 @@
-**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**
-<br/>
+---
+outline: deep
+---
 
-## How to use
+**The Services section is where you set up monitoring for external websites or servers using Agents.**  
+**Configured service monitors can be viewed on the "Services" page of the homepage, displaying the availability monitoring results for the past 30 days.**
 
-To add a new monitor, you can go to the "Services" page in the administration panel and click "Add Service Monitor".  
+## How to Use
 
-To add a service monitor, you need to complete the following settings:
-+ `Name` - Customize a name    
+To add a new monitor, go to the "Services" page in the Admin Panel and click "Add Monitor."
 
-+ `Type` - Select a monitoring type. Nezha currently supports three monitoring types: "HTTP-GET", "ICMP-Ping" and "TCP-Ping".
+When adding a new service monitor, you need to set the following parameters:
 
-+ `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  
+- **Name**: Customize a name.
 
-> + `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 
+- **Type**: Select a monitor type. Nezha Monitoring currently supports three types: "HTTP-GET," "ICMP-Ping," and "TCP-Ping."
 
-> + `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  
+- **Target**: Depending on the type you choose, the method for setting the target differs:
+  - `HTTP-GET`: For this type, you should enter a URL as the target, including `http://` or `https://`. **If your target URL is `https://`, the SSL certificate of that URL will also be monitored. Notifications will be triggered when the SSL certificate expires or changes.** Example: https://example.com.
+  - `ICMP-Ping`: For this type, you should enter a domain name or IP without a port number. Example: 1.1.1.1 or example.com.
+  - `TCP-Ping`: For this type, you should enter a domain name or IP with a port number. 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  
+- **Request Interval**: Set the interval in seconds at which the Agent requests the target.
 
-+ `Coverage`： Select a rule to determine which Agents to use to send requests to the target  
+- **Coverage**: Select a rule to determine which Agents will request the target.
 
-+ `Specific Servers`： Use with coverage to select the Agent to be excluded from the rule  
+- **Specific Servers**: Used in conjunction with the coverage scope, select Agents within the rule to exclude.
 
-+ `Notification Group`： Select the notification method you have set up on the "Notification" page. [Click here](/en_US/guide/notifications.html#flexible-notification-methods) for more information
+- **Notification Group**: Choose the notification methods you have already set up on the "Notification" page. [Click here](/en_US/guide/notifications.html#flexible-notification-methods) for more details.
 
-+ `Enable Failure Notification`： Select whether to receive target failure notifications as needed, default is inactive  
+- **Enable Fault Notification**: Choose whether to receive fault notifications for the target as needed. The default is unchecked.
 
-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  
-<br/>
+After setting it up, click "Add." Wait a moment and go to the "Services" page on the homepage to view the monitoring results.
 
-## Notification of delay changes
-Nezha Monitoring monitors and statistics the delay between the Agent and the target server, and sends notifications in case of significant changes    
-Use this feature to help you monitor your server's routes for changes  
+## Latency Change Notification
 
-+ `Enable delay notifications`：When enabled, notifications will be sent when the Agent to target server delay is higher than the `Max delay` or lower than the `Min delay`  
-<br/>
+Nezha Monitoring can monitor and record the latency between the Agent and the target server, sending notifications when there are significant changes. This feature helps you monitor if the server's network route has changed.
 
-## Management Monitor
-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  
\ No newline at end of file
+- **Enable Latency Notifications**: When enabled, Notification will be sent if the latency from the Agent to the target server is greater than the `Maximum Latency` or less than the `Minimum Latency`.
+
+## Trigger Tasks on Notification
+
+If you need to execute tasks when service monitoring Notification are triggered, you can check "Enable Trigger Tasks" and select the pre-configured trigger tasks in "Task on Notification" and "Task on Recovery."
+
+## Network Latency Chart
+
+The TCP-Ping and ICMP-Ping monitoring types set in the Services page will automatically enable the monitoring chart feature. On the "Network" page of the homepage, you can view historical network latency charts. The data in the charts is based on the latency from the Agent to the target server. You can click the Agent's name to toggle the chart display. In the chart, you can uncheck the target server's name to hide or show the corresponding data.
+
+## Managing Monitors
+
+To manage existing service monitors, go to the "Services" page in the Admin Panel. Select a monitor configuration and click the icons on the right to edit or delete it.
\ No newline at end of file
diff --git a/docs/guide/services.md b/docs/guide/services.md
index 58dc199e..9752fe52 100755
--- a/docs/guide/services.md
+++ b/docs/guide/services.md
@@ -3,59 +3,49 @@ outline: deep
 ---
 
 **服务区域是设置 Agent 监控外部网站或服务器的功能设置区**  
-**设置好的服务监控可以在主页中的 “服务” 页查看过去 30 天的可用性监控结果**  
-<br/>
+**设置好的服务监控可以在主页中的“服务”页查看过去 30 天的可用性监控结果**  
 
 ## 使用方法
 
-如需新增一个监控，可以进入管理面板中的 “服务” 页，点击“添加监控”  
+如需新增一个监控，可以进入管理面板中的“服务”页，点击“添加监控”。
 
-新增一个服务监控，你需要设置以下参数：  
-+ `名称` - 自定义一个名称  
+新增一个服务监控时，你需要设置以下参数：  
 
-+ `类型` - 选择一个监控类型，目前哪吒监控支持三种监控类型，分别是 “HTTP-GET”、“ICMP-Ping” 和 “TCP-Ping”
+- **名称**：自定义一个名称。
 
-+ `目标` - 根据你选择的类型不同，目标的设置方法也不同
-> + `HTTP-GET`: 选择此类型，你应该输入一个URL作为目标，URL需添加 `http://` 或 `https://` **如果你的目标URL是 `https://` ,将会同时监控该URL的SSL证书，当SSL证书到期或发生变更，会触发提醒**  
-例如： https://example.com  
+- **类型**：选择一个监控类型。目前哪吒监控支持三种监控类型，分别是“HTTP-GET”、“ICMP-Ping”和“TCP-Ping”。
 
-> + `ICMP-Ping`: 选择此类型时，你应该输入一个域名或IP，不含端口号  
-例如：1.1.1.1 或 example.com 
+- **目标**：根据你选择的类型不同，目标的设置方法也不同：
+  - `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。
 
-> + `TCP-Ping`: 选择此类型时，你应该输入一个域名或IP并包含端口号  
-例如：1.1.1.1:80 或 example.com:22  
+- **请求间隔**：设定 Agent 每次请求目标的时间间隔，以秒为单位。
 
-+ `请求间隔`： 设定 Agent 每次请求目标的时间间隔，以秒为单位  
+- **覆盖范围**：选择一条规则来确定要使用哪些 Agent 来请求目标。
 
-+ `覆盖范围`： 选择一条规则来确定要使用哪些 Agent 来请求目标  
+- **特定服务器**：配合覆盖范围使用，选择规则内需要排除的 Agent。
 
-+ `特定服务器`： 配合覆盖范围使用，选择规则内需要排除的 Agent  
+- **通知方式组**：选择你已经在“告警”页设置好的通知方式，[点击这里](/guide/notifications.html#灵活的通知方式)了解详情。
 
-+ `通知方式组`： 选择你已经在 “告警” 页设置好的通知方式，[点击这里](/guide/notifications.html#灵活的通知方式)了解详情
+- **启用故障通知**：根据需要选择是否接收目标故障通知，默认为不勾选。
 
-+ `启用故障通知`： 根据需要选择是否接收目标故障通知，默认为不勾选  
-
-设置完成后，点击 “添加” 即可  
-稍等片刻前往主页的 “服务” 页，查看监控结果
-<br/>
+设置完成后，点击“添加”即可。稍等片刻前往主页的“服务”页查看监控结果。
 
 ## 延迟变化告警
-哪吒监控可以监测并统计 Agent 到目标服务器之间的延迟，在发生较大变化的情况下发送通知    
-利用此功能可以帮助你监控服务器的线路是否发生了变化  
 
-+ `启用延迟通知`： 开启时，当 Agent 至目标服务器的延迟大于`最高延迟`或小于`最低延迟`时，将会发送告警通知  
-<br/>
+哪吒监控可以监测并统计 Agent 到目标服务器之间的延迟，在发生较大变化的情况下发送通知。利用此功能可以帮助你监控服务器的线路是否发生了变化。
+
+- **启用延迟通知**：开启时，当 Agent 至目标服务器的延迟大于`最高延迟`或小于`最低延迟`时，将会发送告警通知。
 
 ## 告警时触发任务
-如果你需要在服务监控告警触发时执行一些任务，可以勾选 “启用触发任务”
-并在“告警时触发任务”和“恢复时触发任务”中选择你已经提前设置好的触发任务
+
+如果你需要在服务监控告警触发时执行一些任务，可以勾选“启用触发任务”，并在“告警时触发任务”和“恢复时触发任务”中选择你已经提前设置好的触发任务。
 
 ## 网络延迟图表
-在服务页中设置的 TCP-Ping 和 ICMP-Ping 类型的监控都会自动启用监控图表功能  
-在主页的 “网络” 页中，你可以查看历史网络延迟监控图表  
-图表中的数据是根据 Agent 到目标服务器的延迟统计而来，你可以点击 Agent 的名称来切换图表   
-在图表中，可以取消勾选目标服务器的名称来隐藏或显示对应的数据
+
+在服务页中设置的 TCP-Ping 和 ICMP-Ping 类型的监控都会自动启用监控图表功能。在主页的“网络”页中，你可以查看历史网络延迟监控图表。图表中的数据是根据 Agent 到目标服务器的延迟统计而来，你可以点击 Agent 的名称来切换图表。在图表中，可以取消勾选目标服务器的名称来隐藏或显示对应的数据。
 
 ## 管理监控
-如需对已有的服务监控进行管理，可以前往管理面板中的 “服务” 页  
-选择一条监控配置，点击右侧的图标进行编辑或删除
\ No newline at end of file
+
+如需对已有的服务监控进行管理，可以前往管理面板中的“服务”页。选择一条监控配置，点击右侧的图标进行编辑或删除。
\ No newline at end of file