comment on

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

«The Crux of the Biscuit is the Apostrophe»

In reply to Re: Perl local dashboard? by karlgoethebier
in thread Perl local dashboard? by flieckster

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks