It would be nice to measure some things out of kumascript: * Response times in performing macro evaluation for documents * Execution times of individual templates * Most-used templates * Templates reporting the most errors * Documents reporting the most errors More? Seems like statsd would be the easiest way to get this measured in kumascript, so we can see pretty graphite graphs.
Severity: normal → enhancement
Hmm, maybe this isn't a blocker to kumascript launch. But, might be nice to have shortly thereafter.
Something else to measure: * Cache hits / misses in general, per page, per template, etc
Just making sure you guys know: Jake mentioned that we should be all set to use the Graphite server in PHX1.
Estimating points even though the PR is already in.
Whiteboard: s=2012-07-25 → s=2012-07-25 p=2
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/7bbdaded0b25f7b34d462cbbd61cecabefe1c7dd bug 734495: update kumascript to use statsd, disabled by default in vagrant (so far) https://github.com/mozilla/kuma/commit/2696b414bfe431ed4f52ac1a72ac93a7ea742fac Merge pull request #429 from lmorchard/more-events-and-measurements bug 734495: update kumascript to use statsd, disabled by default in vagrant (so far)
This has been merged. It will probably need further adjustment, but that should drive follow-up bugs
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Agreed. Thank you for taking care of this, guys!
Component: Docs Platform → Editing
Product: Mozilla Developer Network → Mozilla Developer Network
You need to log in before you can comment on or make changes to this bug.