Open Lan-Hekary opened 2 years ago
Hi,
first of all, thanks a lot for the suggestions!
The original idea for the status pages was to provide a public status for a service/website. It seems like many of our users use them differently though: More as a dashboard for themselves to have an overview service operations. In that context, the suggestions make sense to me - for the original use case, they might not make sense for most people.
Let me think about it a bit and do some more research on how people are using this feature.
Of course, any input is appreciated.
Patrick
Hello @pschlan, Any News about these suggestions ?
Hello, I recently started using cron-jobs.org, and I am amazed by what it can do. your amazing service gives me the peace of mind that my API is working properly over long periods of time. How awesome!!
I Have some Suggestions that will improve the user experience even more:
I suggest you add some kind of UI section to the status page that Shows that last response that the API returned. so if an API returns some kind of log msg or any other content, we can view it immediately in the status page. The data is already stored for the last 25 Request anyway and is available in the Dashboard.
Further more, if the API returns JSON Object (Most of them do actually) you can Prettify it to make it easier to read using some kind of Client side library for that with no additional cost to the performance. Other MIME types can be displayed as plain text or if possible displayed using their respective representation tools.
Looking forward to hearing you comments on these suggestions. Thanks.