| To: | Benjamin De Cock <dcbenjamindc@xxxxxxxxx> |
|---|---|
| Subject: | Re: Possible bug in pmwebapi |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Thu, 24 Mar 2016 13:15:53 -0400 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <CAMELWYkdd98SqBVBCWZGwW3AVgva+yHK3v4r1r=SYUqon8xdvA@xxxxxxxxxxxxxx> (Benjamin De Cock's message of "Mon, 21 Mar 2016 15:02:30 +0100") |
| References: | <CAMELWYkdd98SqBVBCWZGwW3AVgva+yHK3v4r1r=SYUqon8xdvA@xxxxxxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
dcbenjamindc wrote: > I noticed a strange behaviour of the pmwebapi interface > Consider this example: > http://hostname4:44323/pmapi/context?hostname=localhost <-- context = hostname > [...] > http://hostname4:44323/pmapi/1247214105/_fetch?names=hotproc.memory.size <-- > hotproc namespace = nok > {"timestamp":{"s":1458567973,"us":760073 }, "values":[]} <-- empty > [...] OK. > Whereas on the host: > perftest@hostname4:~$ pminfo | grep hotproc.memory.size <-- hotproc captured = > ok > [...] That's not an apples-to-apples comparison. pminfo talks to "-h local:" by default. If you make your pmwebd context use "/pmapi/context?hostname=local:", it'll give you the same information. If your copy of pmwebd doesn't let you connect to local:, add "-P" (permissive [sic] mode) to the pmwebd.options and restart it. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] GSOC 2016 idea for PCP, Charles Cui |
|---|---|
| Next by Date: | pcp update: pmwebd older msie compatibility, Frank Ch. Eigler |
| Previous by Thread: | Possible bug in pmwebapi, Benjamin De Cock |
| Next by Thread: | [Bug 1304722] pcp pmda subrpm remove should trigger ./Remove script, bugzilla |
| Indexes: | [Date] [Thread] [Top] [All Lists] |