scriptactivity failures to show last successes of the given script
Bug #656728 reported by
Steve McInerney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Almost every time we have a reported failure via scriptactivity, one of the very first steps I'll do in the initial triage is "when was the script last successful; and how long did it take to run".
Which is achieved via SQL on the prod database.
It seems it would be most useful to avoid this manual step, and have this information pre-provided in the initial report.
eg https:/
Suggest that the columns needed are: hostname, date_started, date_completed and time taken (for the math challenged).
A limit of 5 or 10 should generally be enough information to get a feel for previous runs and establish a level of "what is normal".
tags: | added: canonical-losa-lp |
Changed in launchpad: | |
importance: | Medium → Low |
To post a comment you must log in.
Thanks to Diogo, here's some background to the request.
Steve is probably talking about the emails with the subjects like "Scripts failed to run: ..."
These emails are generated by scripts/ script- monitor. py (and maybe scripts/ script- monitor- nagios. py is related?)
Sounds like a good idea.