graph server stats for package importer machine

It's probably already tracked in Nagios for the sysadmins, or will be
when we move machines. So we should focus on doing things that will
help us improve the service, like:
 * number of passed/failed/unchanged imports
 * load?
 * average length of time per job?
 ...?

--
Martin

BTW - bugs generally won't get sysadmin work done - is there an RT instead?

On 22 July 2010 17:46, Robert Collins <email address hidden> wrote:
> BTW - bugs generally won't get sysadmin work done - is there an RT
> instead?

There's no point filing an RT until we know precisely what we want,
and little point filing a bug asking for changes to tuolumne that we
could do ourselves.

--
Martin

On Thu, Jul 22, 2010 at 6:11 PM, Martin Pool <email address hidden> wrote:
> On 22 July 2010 17:46, Robert Collins <email address hidden> wrote:
>> BTW - bugs generally won't get sysadmin work done - is there an RT
>> instead?
>
> There's no point filing an RT until we know precisely what we want,
> and little point filing a bug asking for changes to tuolumne that we
> could do ourselves.

I was referring to the move, which we do know about.

-Rob

On Thu, 22 Jul 2010 16:11:01 -0000, Martin Pool <email address hidden> wrote:
> On 22 July 2010 17:46, Robert Collins <email address hidden> wrote:
> > BTW - bugs generally won't get sysadmin work done - is there an RT
> > instead?
>
> There's no point filing an RT until we know precisely what we want,
> and little point filing a bug asking for changes to tuolumne that we
> could do ourselves.

See RT#37046.

Let's close that if it's not the way to go about this.

Thanks,

James

On 22 July 2010 18:49, James Westby <email address hidden> wrote:
> On Thu, 22 Jul 2010 16:11:01 -0000, Martin Pool <email address hidden> wrote:
>> On 22 July 2010 17:46, Robert Collins <email address hidden> wrote:
>> > BTW - bugs generally won't get sysadmin work done - is there an RT
>> > instead?
>>
>> There's no point filing an RT until we know precisely what we want,
>> and little point filing a bug asking for changes to tuolumne that we
>> could do ourselves.
>
> See RT#37046.
>
> Let's close that if it's not the way to go about this.

I'll turn it into a tuolumne mp, but let's leave it open til I'm done.

What is the human meaning of the long sql query in that rt? (ie what
should i call the graph?)

--
Martin

On Thu, 22 Jul 2010 17:36:17 -0000, Martin Pool <email address hidden> wrote:
> I'll turn it into a tuolumne mp, but let's leave it open til I'm done.
>
> What is the human meaning of the long sql query in that rt? (ie what
> should i call the graph?)

"One that jml told me to request"

I'm pretty sure that it is the number of packages without a development
focus, as in the number of packages that we have failed to ever import.

Thanks,

James

https://code.edge.launchpad.net/~mbp/tuolumne-lp-configs/spph/+merge/30757
(private)

I'll close the rt.

--
Martin

The output of jml's suggested query is now graphed in <https://lpstats.canonical.com/graphs/UddSourcePackagesWithoutBranches/> (private). I told Francis he can close the RT. However, this bug as a whole isn't really closed, because this doesn't give a very complete picture of the package importer.