pcp
[Top] [All Lists]

Re: pmwebd: Defining the directory for PCP Archives

To: Chandana De Silva <chandana@xxxxxxxxxxxxx>
Subject: Re: pmwebd: Defining the directory for PCP Archives
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Sat, 6 Dec 2014 20:06:56 -0500
Cc: "pcp@xxxxxxxxxxx" <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1417903963.20915.10.camel@tardis>
References: <y0ma9376psv.fsf@xxxxxxxx> <1417499687.17867.23.camel@tardis> <20141202121245.GP5088@xxxxxxxxxx> <1417556631.941.12.camel@tardis> <20141202230914.GQ5088@xxxxxxxxxx> <1417647290.948.20.camel@tardis> <20141205151437.GD5088@xxxxxxxxxx> <1417898573.20915.7.camel@tardis> <20141206212156.GE5088@xxxxxxxxxx> <1417903963.20915.10.camel@tardis>
User-agent: Mutt/1.4.2.2i
Hi -

> OK, I do see data when I use the JSON format. Does this look right ?

>[{"target":"-2F-var-2F-logdata-2F-pmlogger-2F-archdb1-2E-prd-2E-mel-2F-20141121-2E-meta.mysql.status.aborted_clients",
>"datapoints":[[null, 1417816509],[null, 1417816594] [...]

Well, that's an awful lot of nulls (missing data, so the time window
is probably wrong for that archive), but in principle it's fine.


- FChE

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