Hi Frank,
On Mon, Oct 13, 2014 at 03:02:14PM -0400, Frank Ch. Eigler wrote:
> > - pmwebd returns empty values :
>
> > GET /pmapi/747499891/_fetch?pmids=79691786 HTTP/1.1
> > [...]
> > { "timestamp": { "s":1413224370, "us":801625 },
> > "values": [
> > ] }
>
> How was that context 747499891 created? /pmapi/context?local=ANYTHING
> is not the same thing; use /pmapi/context?hostname=local: instead.
> Perhaps pmwebd should default to -h local: (and support an unparametrized
> /pmapi/context?) the same way pm* clients do. Opinions?
Ah there you go. I am attaching a patch to the man page, to make it slightly
more obvious and to cleanse away my API sins. I failed to notice the
difference between the two ;)
Personally, I think -h local: is a bit more obvious and expected, but as
long as it's somehwat clearer in the pmwebapi man page, I'm fine with
the status quo.
Thanks again,
Michele
--
Michele Baldessari <michele@xxxxxxxxxx>
C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D
0001-Clarify-the-limits-of-PM_CONTEXT_LOCAL-when-using-pm.patch
Description: Text document
|