On 10/14/2013 06:11 AM, Evan Dandrea wrote:
It's now possible to send metrics on m-o via statsd such that they show up on http://graphite.engineering.canonical.com.
Note that you can also drive this from the shell: evand@magners-orchestra:~$ echo "ubuntu-ci.testing.key:1|c" | nc -w 1 -u snakefruit.canonical.com 10041
This was a good read. I've been toying around with it a little and was thinking about how we might hook this up in the context of daily image testing (or to get started on our staging server). I'm a little unsure of how much/little you should go with the heirarchies (or if it matters). ie - is there a good way to start so things scale sanely.
for the staging instance where we have the new "test execution service" job. I was thinking about some metrics like:
ubuntu-ci.staging.touch-execution-service.total_tests (counter) ubuntu-ci.staging.touch-execution-service.autopilot_tests (counter) ubuntu-ci.staging.touch-execution-service.job_duration (timer) ubuntu-ci.staging.touch-execution-service.provision_duration (timer) would this make sense? -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
