-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Current Status? #11
Comments
there is no end point that returns this specific info but u can know that from /ping or /uptime , in the mean time ill try to add it, thnx for the contribution. |
Could you please share how do I get up/down status for specific monitor? |
actually this was my main point to look at this ! |
Would be nice if we use the /monitors it'll include beats in a serpeate json object for each monitor. |
This would make the object too big on large-scale deployments. From there you query every monitor individually for granular control. In my example I have over 600 monitors. The JSON produced will be absolutely ineffective to process. |
I notice that the response is in relation to Uptime-Kuma itself and not the status of the actual monitor. And in my case returns 200, not "true" Currently I am processing the last beat in /monitors/{monitor_id}/beats How to get last beat in JSAs if jsonResponse is the raw json from the API |
I could very well be just over looking this, but where can I pull current monitor status from? ie is a monitor "up or down"?
The text was updated successfully, but these errors were encountered: