Frank Elsinga

As always: We are open to PRs, here is our [contribution guide](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md). Note that - a Pull request should be class extending `MonitorType` instead of the currently primary approach of...

@vslinuxdotnet https://github.com/louislam/uptime-kuma/pull/2693 has been merged and is avaliable in `1.22`. I think this issue is resolved. Could you close this issue?

@ We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/pull/2693 https://github.com/louislam/uptime-kuma/issues/1089 https://github.com/louislam/uptime-kuma/issues/2487 as there is no functional difference...

@louislam @BercziSandor given that https://github.com/louislam/uptime-kuma/pull/3441 was merged, I think we can safely close this one too ^^

@Termex69 I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2231 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?...

Closing as duplicate of https://github.com/louislam/uptime-kuma/issues/2231

@Takenfal I have edited your FR to remove already implemted/tracked otherwise FRs - User manageement: #128 - mutli-incidents: https://github.com/louislam/uptime-kuma/issues/862 and https://github.com/louislam/uptime-kuma/issues/2389 - Start timestamp and End timestamp on the beats...

That is a pretty creative abuse of said bug. The reason this exists/"works" is that the monitoring data is not wiped on switching to another monitoring type and the frontend...

@ItIzJR Could you close this PR? https://github.com/louislam/uptime-kuma/pull/3571 implements the same feature, but is more mature ⇒ has a chance of getting merged ^^

Related #2234