Louis Lam

@Rewt0r I resolved the problem by adding the mysql-community repo. (Linux things are killing me in deep) ``` sudo rpm -Uvh http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm ```

> Some things, like that which is visible on the status page, are already readily accessible, just undocumented. The creation and deletion of monitors/notifications are some of the things that...

Yes, I see your point. I won't implement two sets of APIs, but as of 1.8.0, I labeled them as "internal APIs" that everyone should not use. In the future,...

I may prefer making this harder to be set. Maybe we can add a env var `UPTIME_KUMA_DISABLE_INTERVAL_LIMIT`. If user set it to true, they can set a small interval.

It is because setting it to very low likely causes issues such as random timeout, very high cpu usage, very high database usage and the database locking issue. Uptime Kuma...

I just tested it with 1 second, it was so unstable and my Uptime Kuma was under heavy loading and slow response. The monitor is dead even I changed back...

> In this case, it would be important that this feature is activated in the graphical environment and that when doing so, a large warning appears indicating the possible consequences....

Looking for a tester who are using prometheus to test this pull request.

I checked the source code. Since `addMonitorTag` is a separated call which I guess it called after `addMonitor`. That means when the monitor saved and restarted internally, at this moment,...

> I checked the source code. Since `addMonitorTag` is a separated call which I guess it called after `addMonitor`. That means when the monitor saved and restarted internally, at this...