Frank Elsinga

> Any chance to have some custom informational status? No other monitor has informational satuses and this does not really fit into our model of important and not important events.

Actually, your core issue is that how you would like to run things (1 monotor = n things being monitored) does not work with how we recomend to do things...

Issue should be resolved in https://github.com/louislam/uptime-kuma/releases/tag/2.0.0-beta.0

> Considering this is not a stable release [..] feels a little early to be closing this issue as being fixed All other issues (such as switching the tag in...

@ljluestc Am I missing something? Where does `C++` come fit into this issue? `sqlx` is written in rust and SQLite3 is written in `C`..

Regular debugging step is to enable dns caching in the settings for this issue. We by default don't cache and some dns servers don't like this => `getaddrinfo EAI_AGAIN` If...

We will under the current architecture only use one core.

Agree that if a CNAME exists that we should handle this case better. The code for this is located here if you want to provide a PR ^^ https://github.com/louislam/uptime-kuma/blob/master/server/monitor-types/dns.js

I think what you are asking about (especially given the asked git integration) is likely better served by a CI-piepeline

Yes, docs on this structure could be improved, but hey. > {{description}} Please see `monitorJSON.description`. > {{group}} Depending on what you want, we have this at differerent places: - `monitorJSON.path`:...