Frank Elsinga

I think this is better tracked in https://github.com/louislam/uptime-kuma/issues/4233, as docker-compose and docker swarm are likely not as different or https://github.com/louislam/uptime-kuma/issues/957 for the docker-. => merging these issues via closing this...

@wechsler42 @asyba @casudo Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing **what needs to be done how...

Closing as resolved by https://betterstack.com/community/questions/how-to-redirect-docker-logs-to-file/ as commented above

Please subscribe to this issue instead https://github.com/louislam/uptime-kuma/issues/1388 I think adding this would require https://github.com/louislam/uptime-kuma/issues/646 first

@aphex008 Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing **what needs to be done how by whom**....

v2 does include a lot of perfomance updates and should allow scaling past ~200-500 monitors. See https://github.com/louislam/uptime-kuma/milestone/24 for further progress

@hrshv6 **Completely unrelated to the other posts.** NONE of them have stated that they are using haproxy. This post is about connection timeouts caused by the now removed import/export functionality...

@BoyanBlagoev the keyword field does currently not have this as an option. Reasonable implementations would likely get accepted though. @JulianGro The reason this is getting closed is, that this is...

I think this is a duplicate of #2735 or #631 which are using the correct issue template and in gerneral have recieved more traction. If you agree, could you please...

@JulianGro We resolve `help` issues after 3 month They are also not being locked as in the article you posted As mentioned above (which you agreed with) this issue is...