As ikegami already mentioned a script doesn’t have a status.But it can have some kind of pseudo-status if we write 1 or 0 to a flat file or some database. Which could mean it was executed with success or not. That’s what a monitoring system does all the time. If something goes wrong a event handler is triggered to fix the issue. Probably that’s the point you missed.

And if things still go wrong some admin must fix it by hand via the command line.

Summary: Normally such things are done by a monitoring system or cron and not manually via a dashboard. Dashboards are more made for the customer, management and first level support. And they are made to make them feel good and not for interaction.

I hope I didn’t miss the point and that this is helpful.

Best regards, Karl

I have a system that runs scripts via a cron all day, and i'd like a place to show status of scripts running. ie if they err or didn't run for a reason so anyone can log on and see status. Ideally i'd love to also trigger the script from this interface so no one touches the actual script file, but can run adhoc as needed. I was hoping there was some sort of cron dashboard that would show this.

Surely this would depend on how your existing scripting logs all of these things, which would mean such a dashboard would be quite specific to you. Mojolicious::Lite would be my first port of call.

In that case (of Cron), there is Crab written in Python. To trigger a job, time to run it can be modified via its web interface; do not know if there is a way to do one-off run. IIRC one may need to Crabify the crontabs of interest.

Unfortunately no. I guess you need to write your own dashboard for this. But what exactly do you want to do? Has it something to do with monitoring? Regards, Karl

... on the same line, do the scripts run via cron?

Good point. But you should have better asked the OP. Best regards, Karl

«The Crux of the Biscuit is the Apostrophe»

What do you mean by "the status of a script"? A script is just a file. It doesn't have a status.