Frank Elsinga

Closing as resolved by https://github.com/louislam/uptime-kuma/pull/2693 in the [`1.22`-release](https://github.com/louislam/uptime-kuma/releases/tag/1.22.0).

@david-plugge what feature are you missing? It seems to me that the feature you are referring to already exists. (as commented by @flammable) If this issue is resolved, could you...

See https://github.com/louislam/uptime-kuma/wiki/How-to-Monitor-Docker-Containers This remote docker montioring currently exists => closing as resolved

I think the basic usecase (monitoring one thing from mutliple sides) behind this feature can also be resolved via ripe atlas. I know that this is somewhat limited for (very...

> It would be nicer to have a storage backend like HA Postgres or CockroachDB but since uptime-kuma currently only seems to support file system storage Actually, v2 does support...

I don't know what you need. The sqlite database is stored at `db/kuma.db`. SQLite does not really have a connection string I know of... you just point at the file...

There have not been any news in the last four months. We are still working out the kinks of V2.0

@JaneX8 You can subscribe to https://github.com/louislam/uptime-kuma/issues/84 for updates. Currently, our priorities are on different items such as #4500 and refactoring the monitoring items for better maintainability.

What we need is a CURRENT, publicly accessible (=reproducible) testcase. The first part of this issue was resolved when we switchd from cachable lookup to NSCD `(Name Service Cache Daemon)`...

If you want, you can provide a PR to make this setting configurable in the notification providers settings. Our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/237a6e8da9ac492baa3f68a4db4679bf7ec833e6/CONTRIBUTING.md