@nichu42 said in App Error / Status Page:
@nebulon said in App Error / Status Page:
Not sure if uptime kuma can be scripted that way to extract health and runState from the json result.
It appears to me that neither JSON key matching nor Regex are implemented yet, but there are open issues for both.
I was just taking the advice from @JLX89 because I felt that checking for runState might not be enough. But could you please explain the check behind health=healthy?
I've had it setup using the following and it seems to have been working, if the app goes offline it is reflected in Uptime Kuma.
Monitor Type: HTTPS(s) - Keyword
URL: Cloudron API URL
HTTP Options - Method: "GET"
I'm assuming you could probably pull either of the following based on the Cloudron API documentation: "runState": "running" or "health": "healthy"?
This at least seems to be working for me -- but could be a better way of doing this. The obvious downfall is if you're tracking uptime rather than just status if you make config changes or need to restart the app this is reflected -- so we bumped up the heartbeat retry levels.