Closed
Bug 847104
Opened 11 years ago
Closed 8 years ago
Implement a KumaScript dashboard
Categories
(developer.mozilla.org Graveyard :: KumaScript, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sheppy, Unassigned)
Details
(Whiteboard: [specification][type:feature])
What problems would this solve? =============================== We should have a KumaScript dashboard that would let admins look at the state of the KumaScript engine, look at any error logs, and if necessary restart the KumaScript service. This would help us resolve KumaScript related problems without relying heavily on IT or the dev team. Who would use this? =================== MDN admins. What would users see? ===================== The specific design is something that needs to be worked out. This could be done as part of the Django admin section though. What would users do? What would happen as a result? =================================================== Options provided should include: * View KumaScript logs * See how much system resources KumaScript is using * Kill a KumaScript service (useful for runaway scripts, which can happen, or when KumaScript explodes, which happens only rarely but does also happen) * Look at statistics about how many scripts run, what the most commonly run scripts are, etc. Is there anything else we should know? ======================================
Updated•10 years ago
|
Component: General → KumaScript
Updated•10 years ago
|
Severity: normal → enhancement
Comment 1•8 years ago
|
||
KumaScript is now in NewRelic and there is the project bug 1235409 for more perf tracking.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•