建议增加被动监测功能

[aloasut]

我看类似的监控工具都是主动探测的，我觉得需要增加一个被动的功能。 可以参考的是 https://healthchecks.io/

被动监测的玩法： 需要监测的服务定期通过http接口向监控机上报数据，或者仅仅是报个平安。一段时间没有报，或者数据有误，就发警报。

被动监测的用途： 1.apm位于公网，需要监测的服务位于内网。 2.简化告警逻辑，什么情况下需要告警由上报机决定。 3.上报机可以crontab跑脚本，可以通过monit跑比较复杂的逻辑。

举例： 1.每天跑mysql备份，备份完告诉监控机我备份完了 2.内网通过数据库监控某一条数据，定期告诉监控机这条数据还OK 3.家庭内网跑个脚本监测动态拨号的IP，有更新了告诉监控机，这个比监控机监控ddns更新方便。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

I see that similar monitoring tools are actively detected, and I think a passive function needs to be added. You can refer to https://healthchecks.io/

The gameplay of passive monitoring: The services that need to be monitored regularly report data to the monitoring machine through the http interface, or just report safety. If there is no report for a period of time, or the data is wrong, an alarm will be issued.

Uses of passive monitoring:

1. apm is located on the public network, and the services to be monitored are located on the intranet.
2. Simplify the alarm logic, and the reporting machine determines when an alarm is required.
3. The reporting machine can run scripts on crontab, and can run more complex logic through monit.

Example:

1. Run mysql backup every day, tell the monitoring machine that I have finished the backup after the backup
2. The intranet monitors a certain piece of data through the database, and regularly tells the monitoring machine that this data is OK
3. Run a script on the home network to monitor the IP of the dynamic dial-up, and tell the monitoring machine if it is updated. This is more convenient than monitoring the ddns update by the monitoring machine.

[tomsun28]

thanks 👍 很用心的建议 我们参考 https://healthchecks.io/ 研究下

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

thanks 👍 Very thoughtful suggestion, we refer to https://healthchecks.io/ for research