| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] pcp update: json pmda |
| From: | Mark Goodwin <goodwinos@xxxxxxxxx> |
| Date: | Wed, 10 Jun 2015 12:06:13 +1000 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <50220216.14907471.1433901374432.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <20150609004114.GA9357@xxxxxxxxxx> <557641A2.7040801@xxxxxxxxx> <20150609020038.GB9357@xxxxxxxxxx> <5576D75E.2010205@xxxxxxxxxx> <50220216.14907471.1433901374432.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
On 06/10/2015 11:56 AM, Nathan Scott wrote: ... maybe capture an archive .. and we get PM_ERR_INST when expected, etc.I don't think archives are going to help us here, AIUI this is more of a (live) pmdajson logging-a-bit-too-much kind of issue? For this I ment checking a client tool returns PM_ERR_INST when expected. An archive with the wildly fluctuating indom would make this more deterministic for qa. Cheers |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pcp update: json pmda, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pcp updates: merge kenj (qa updates), Lukas Berk |
| Previous by Thread: | Re: [pcp] pcp update: json pmda, Nathan Scott |
| Next by Thread: | Re: [pcp] pcp update: json pmda, David Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |