Closed Bug 734495 Opened 11 years ago Closed 11 years ago

kumascript: Use statsd in kumascript


( Graveyard :: Editing, enhancement, P2)



(Not tracked)



(Reporter: lorchard, Unassigned)



(Whiteboard: s=2012-07-25 p=2)

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


Seems like statsd would be the easiest way to get this measured in kumascript, so we can see pretty graphite graphs.
Blocks: 659364
Severity: normal → enhancement
Hmm, maybe this isn't a blocker to kumascript launch. But, might be nice to have shortly thereafter.
No longer blocks: 659364
Depends on: 659364
Something else to measure:

* Cache hits / misses in general, per page, per template, etc
No longer depends on: 659364
Blocks: 710728
Priority: -- → P2
Blocks: 756266
No longer blocks: 710728
No longer blocks: 756266
Blocks: 756266
Blocks: 772468
Whiteboard: s=2012-07-17
Just making sure you guys know: Jake mentioned that we should be all set to use the Graphite server in PHX1.
Whiteboard: s=2012-07-17 → s=2012-07-25
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
bug 734495: update kumascript to use statsd, disabled by default in vagrant (so far)
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
Closed: 11 years ago
Resolution: --- → FIXED
Agreed. Thank you for taking care of this, guys!
Version: Kuma → unspecified
Component: Docs Platform → Editing
No longer blocks: 756266
See Also: → 1235409
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.