增加faq和三方工具链接 (#82)

docs/en_US/guide/dashboardq.md

@@ -72,6 +72,16 @@ The value entered for the DDNS provider is incorrect. Currently, only `webhook`,
 
 The entered DDNS `AccessID` or `AccessSecret` is incorrect.
 
+## Dashboard warning: NEZHA>> 错误的服务监控上报...
+
+1. The installed versions of the Dashboard and Agent are not compatible and have a `TaskType` that is unsupported by its counterpart. Updating both to the latest version could solve this problem.
+
+2. This could be a specific issue in Dashboard v0.17.10 - v0.18.0. Updating to the latest version could solve this.
+
+## Unable to start the Agent service: Unix syslog delivery error
+
+Appears in Agent v0.16.9+. Mostly caused by a malfunctioning `/dev/log` socket (or it does not exist at all). You can refer to <https://unix.stackexchange.com/questions/317064/how-do-i-restore-dev-log-in-systemdrsyslog-host> to solve this problem. Try avoiding using init systems like `systemd` in a Docker installation.
+
 ## Network Monitoring Page Shows: server monitor history not found
 
 This error indicates that no TCP-Ping or ICMP-Ping type monitoring has been set in the services page or monitoring data has not yet been generated.   

docs/en_US/guide/notifications.md

@@ -265,6 +265,13 @@ For servers with IDs 3 and 4 (defined in ignore), if the monthly outbound traffi
 [{"type":"transfer_out_cycle","max":1099511627776,"cycle_start":"2022-01-01T00:00:00+08:00","cycle_interval":1,"cycle_unit":"month","cover":1,"ignore":{"3":true,"4":true}}]
 ```
 
+::: tip
+If you still have trouble editing rules, you can try the rule generators below to simplify the process. Note that Nezha Monitoring does not guarantee the functionality of these generated rules.
+
+- [Nezha Rule Generator](https://nz.sina.us.kg/): for common cases
+- [Nezha-Traffic-Alarm-Generator](https://wiziscool.github.io/Nezha-Traffic-Alarm-Generator/): for editing cycle traffic rules only and may be more convenient to use. Chinese only.
+:::
+
 ## Notification Trigger Modes
 
 - **Always Trigger**: A notification is triggered every time the Agent reports a status that matches the notification rule.

docs/guide/dashboardq.md

@@ -64,14 +64,24 @@ systemctl status docker
 
 3. 保存配置，并清空浏览器、Nginx、CDN 中的缓存，此时刷新页面应恢复正常。
 
-## 面板无法启动：panic: 无法找到配置的 DDNS 提供者...
+## 面板无法启动：panic：无法找到配置的 DDNS 提供者...
 
 填入的 DDNS provider 的值有误，目前仅支持 `webhook`、`cloudflare`、`tencentcloud` 和 `dummy`。
 
-## 面板更新 DDNS 崩溃：panic: interface conversion: interface {} is nil, not []interface {}
+## 面板更新 DDNS 崩溃：panic：interface conversion: interface {} is nil, not []interface {}
 
 填入的 DDNS `AccessID` 或 `AccessSecret` 有误。
 
+## 面板警告：NEZHA>> 错误的服务监控上报...
+
+1. Dashboard 与 Agent 版本不兼容导致含有对端不支持的 `TaskType` 导致，全部更新至最新版本即可解决。
+
+2. Dashboard v0.17.10 - v0.18.0 也存在此问题，更新至最新版本可以解决。
+
+## 无法启动 Agent 服务：Unix syslog delivery error
+
+此报错见于 Agent v0.16.9+。原因为系统的 `/dev/log` 套接字工作不正常或不存在。可参考 <https://unix.stackexchange.com/questions/317064/how-do-i-restore-dev-log-in-systemdrsyslog-host> 解决。如果使用的是 Docker，请避免使用 `systemd` 等 init 系统。
+
 ## 打开网络监控页显示：server monitor history not found
 
 出现此错误说明没有在服务页中设置 TCP-Ping 和 ICMP-Ping 类型的监控或者监控数据还未生成。   

docs/guide/notifications.md

@@ -300,6 +300,13 @@ ID 为 3 和 4 的服务器（ignore 里面定义），以每月 1 号为统计
 [{"type":"transfer_out_cycle","max":1099511627776,"cycle_start":"2022-01-01T00:00:00+08:00","cycle_interval":1,"cycle_unit":"month","cover":1,"ignore":{"3":true,"4":true}}]
 ```
 
+::: tip
+如果对告警配置仍感到有困难，可以试试以下第三方配置生成器简化操作。哪吒监控不对生成配置的功能性作任何保证。
+
+- [Nezha Rule Generator](https://nz.sina.us.kg/): 适用绝大多数场景
+- [Nezha-Traffic-Alarm-Generator](https://wiziscool.github.io/Nezha-Traffic-Alarm-Generator/): 适用于生成周期流量告警规则，且更加方便一些
+:::
+
 ## 通知触发模式
 
 - **始终触发**：每当 Agent 上报的状态符合告警的规则时，都会触发一次通知。