pcp
[Top] [All Lists]

Re: [pcp] libvirt pmda: add per-device metrics

To: Marko Myllynen <myllynen@xxxxxxxxxx>
Subject: Re: [pcp] libvirt pmda: add per-device metrics
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 2 Oct 2016 16:56:47 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <2d10d43c-a7a2-1488-f6c8-e8ab93e46af9@xxxxxxxxxx>
References: <2d10d43c-a7a2-1488-f6c8-e8ab93e46af9@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 3QoCzXM/uV4HWqMCpD5lpftWHWFcNA==
Thread-topic: libvirt pmda: add per-device metrics
Hi Marko,

----- Original Message -----
> Hi,
> 
> Below is a patch to add support for per-device metrics (for
> VCPU/block/net devices). Nothing too exciting here, the only
> thing to pay attention to is that these clusters now have too
> different indoms, seems to work just fine.

Looks good, working nicely here.

> libvirt.domstats.block.capacity
>     inst [1 or "f01110aa-de20-4f2d-8f98-6ee0bc9de412-block7"] value 1073741824

There's a convention of using "::" as separator for compound instances in other
PMDAs, which would make the above -

  libvirt.domstats.block.capacity
      inst [1 or "f01110aa-de20-4f2d-8f98-6ee0bc9de412::block7"] value 
1073741824

Which is a more clear separator here, and its easier to pick apart in this case
too (via awk/sed/... that is).  If you have a strong preference for the original
way though, no problem going back to that - let me know.  Otherwise, its all in
now - thanks for following up on this.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>