增加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.