On 02/06/14 18:23, John Else wrote:
>
>> - Have you considered using vchan to let other tools capture the rrd stream
>> more easily?
> I hadn't, but I think that could be made to work. At the moment the protocols
> expect the shared-memory resource to be represented as a cstruct so it would
> ne
On 2 Jun 2014, at 18:23, John Else wrote:
> I hadn't, but I think that could be made to work. At the moment the protocols
> expect the shared-memory resource to be represented as a cstruct so it would
> need a bit of tweaking to work with a socket-style interface instead.
Actually thinking abo
On 2 Jun 2014, at 18:23, John Else wrote:
> On 02/06/14 15:48, Anil Madhavapeddy wrote:
>
>> Thanks for the RRD library link -- I hadnt seen this before and it looks
>> very useful for Xen tracing in MirageOS! A few questions while reading
>> through the source:
>>
>> - Rrd_io just exposes a
On 02/06/14 15:48, Anil Madhavapeddy wrote:
> Thanks for the RRD library link -- I hadnt seen this before and it looks very
> useful for Xen tracing in MirageOS! A few questions while reading through the
> source:
>
> - Rrd_io just exposes a single Resource_closed exception and no other values.
On 30 May 2014, at 13:49, John Else wrote:
>
> I've also been working on a library to simplify transmission of RRD data
> (i.e. performance metrics) between domains [1], and integrating this with the
> RRD daemon's plugin library [2].
>
Thanks for the RRD library link -- I hadnt seen this bef
