canonical-ci-engineering team mailing list archive

[Andy Doan <andy.doan@xxxxxxxxxxxxx>]

On 10/22/2013 06:01 PM, Evan Dandrea wrote:
> 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 :)

Hey Guys,

I've got one set of metrics in graphite now that help show how long the 
new "test-execution-service" aka "mega" jobs take. I'm new to this, but 
I believe I've built a report. The URL is insane, so I've used a shortener:

 http://tinyurl.com/ubuntu-ci-mega-times

I wanted to scale these times from ms to minutes, but the resulting 
graph I was generating didn't look right. So for now I look at the 
numbers and divide by 60,000 so that they are easier for me to 
intuitively understand.