canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

On 22 October 2013 15:51, Andy Doan <andy.doan@xxxxxxxxxxxxx> wrote:
> 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)

I wouldn't fret too much about the hierarchy. I'd just pick something
and run with it. In this case, I'd probably flip staging and
touch-execution-service around such that you could have
ubuntu-ci.touch-execution-service.{staging,production}.*

Those look like good metrics. Please wire them up :)

Note that timer will be .timing() in txstatsd:
https://github.com/sidnei/txstatsd/blob/master/txstatsd/metrics/metrics.py#L138

and counter, if I understand your usage correctly will be .gauge() in txstatsd:
https://github.com/sidnei/txstatsd/blob/master/txstatsd/metrics/metrics.py#L87