734495 - kumascript: Use statsd in kumascript

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Editing, enhancement, P2)

Description

[Les Orchard [:lorchard]]

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.

Comment 1

[Les Orchard [:lorchard]]

Hmm, maybe this isn't a blocker to kumascript launch. But, might be nice to have shortly thereafter.

Comment 2

[Les Orchard [:lorchard]]

Something else to measure:

* Cache hits / misses in general, per page, per template, etc

Comment 3

[John Karahalis [:openjck]]

Just making sure you guys know: Jake mentioned that we should be all set to use the Graphite server in PHX1.

Comment 4

[Luke Crouch [:groovecoder]]

Estimating points even though the PR is already in.

Comment 5

[[github robot]]

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)

Comment 6

[Les Orchard [:lorchard]]

This has been merged. It will probably need further adjustment, but that should drive follow-up bugs

Comment 7

[John Karahalis [:openjck]]

Agreed. Thank you for taking care of this, guys!