Frank Elsinga

> You have closed both this issue and the other as completed I think I have made my point that - [mariadb offers encryption at rest](https://mariadb.com/kb/en/data-at-rest-encryption-overview/) (thus we don't need...

@chakflying @louislam @Saibamen @Zaid-maker Currently, we offer pretty basic monitors (grpc, http, dns, docker, databases). I think this monitor does not fit into the line of moniotors we currently offer....

> These 3rd party monitors are hard to maintain, because only our users are checking changelogs for APIs etc. Hi @seluard Thanks for your work, but I don't think this...

Where you are entirely correct is that the current way we are communicating this and how our retry/.. logic for this monitor works is super weird. > [!NOTE] > As...

> letting something go into the pending state isn't really a solution You are explicitly setting it to `PENDING`, so how can you not want the pending state?? I think...

Agree, much nicer. From a UX perspective I feel like switching these two fieds might be benefitial. What do you think? 

Another thing that I forgot in the second review (not adding this would also be fine ^^). Do you think the call-to-action buttons as in `buildActions` from https://github.com/louislam/uptime-kuma/pull/3886 might be...

- > There's already a builtin call-to-action function, you click the message it will jump to the monitor URL. I can't read the text, but could/should these buttons be used...

I think that handling is wrong. In case the url does not exist, the whole `card_action` should not be added. The same goes for `jump_list`: in case no links exist,...

@darkclip I just went over the discussion to look if there is something left open and two things are currently blocking a merge: - I think this part fell under...