Frank Elsinga

Results 1064 comments of Frank Elsinga

@chakflying you are missing a call to action in your descriptions: @karelkryda (only you or Louis can close issues 😉) I believe this issue has been resolved and you can...

@KRider92 The correct envionment variable value is `true` (not `1`). This might have changed in the last 1.5 years, idk. Here are the relevant wiki pages: - setting up iframes:...

![image](https://github.com/louislam/uptime-kuma/assets/26258709/4dee132c-f1e3-45b9-b810-e899c4a5275a) Closing as resolved as this feature was merged by #3312 in `1.23.0`

> a maintenance window feature ??? #1213 was merged and released in `1.19.0`.

First of all: this issue can already be achieved using the `push`-monitor We are consolidating duplicate issues and I think we should track this issue in #84 instead. => closing...

> Can you guys give some ideas on this ![image](https://github.com/louislam/uptime-kuma/assets/26258709/bc70481f-4c2d-4399-8ee3-96f8ef2fefed) This should adhere to the currently configurable state of notifications via reusing the same options. Notifying only once would be...

> Any change this is getting merged soon? As mentioned above: the current implementation is not cutting it, as it would essentially send notifications on every failed attempt and not...

> Will this be available on all http probes? See the files changed => this would be avaliable for all monitors if the problems are adressed

Closing in favor of #4005 (which is on track to be reviewed in `v2.2`)