Skip to content
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

Status Pages Enhancements Suggestions #101

Open
Lan-Hekary opened this issue Nov 24, 2021 · 2 comments
Open

Status Pages Enhancements Suggestions #101

Lan-Hekary opened this issue Nov 24, 2021 · 2 comments

Comments

@Lan-Hekary
Copy link

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.

  • The Final Thought here is to add the option to log a certain JSON Object or a keys inside an Object (or a predefined response).
    then in the status page you can log this variable along side the Availability and the Latency.

Looking forward to hearing you comments on these suggestions.
Thanks.

@pschlan
Copy link
Owner

pschlan commented Nov 25, 2021

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

@Lan-Hekary
Copy link
Author

Lan-Hekary commented Jun 6, 2023

Hello @pschlan,
Any News about these suggestions ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants