G'day Nathan.
Can you please confirm something? I'm guessing you have the mmv pmda
installed, and the pmns contains an entry like
mmv 70:*:*
because without that, the first fetch will return
dbpmda> fetch mmv.test.strings
^ at or near here
Error: Unknown metric name
Type 'help' for a list of commands.
rather than than translating the name to the PMID 70.*.* and then
failing the fetch.
Now if this is the case, then it is simply a bug ... dbpmda just calls
pmLookupName and does not do the while pmcd thing of ... oh! a dynamic
PMID, I need to send it off to the pmda.
The second fetch works because you've used an explicit PMID and skipped
the pmLookupName call in dbpmda.
I'll see what it will take to fix this.
On Wed, 2010-01-13 at 17:23 +1100, Nathan Scott wrote:
> Hi Ken,
>
> Seeing something strange in dbpmda when checking out some new
> MMV client code - the initial fetch failure is the issue...
>
> 17:20 nathans@verge /source/git/pcp/src/pmdas/mmv 308> dbpmda
> dbpmda> open pipe pmdammv
> Start pmdammv PMDA: ./pmdammv
> dbpmda> fetch mmv.test.strings
> PMID(s): 70.*.*
> pmResult dump from 0x9d51170 timestamp: 0.000000 10:00:00.000 numpmid: 1
> 70.*.* (<noname>): Unknown or illegal metric identifier
> dbpmda> pmid mmv.test.strings
> Metric: mmv.test.strings
> 70.2.6
> dbpmda> fetch 70.2.6
> Warning: PMID (70.2.6) is not defined in the PMNS
> PMID(s): 70.2.6
> pmResult dump from 0x9d511d8 timestamp: 0.000000 10:00:00.000 numpmid: 1
> 70.2.6 (<noname>): numval: 2 valfmt: 1 vlist[]:
> inst [0 or ???] value "00oo00"
> inst [1 or ???] value ""
> dbpmda> name 70.2.6
> PMID: 70.2.6
> mmv.test.strings
> dbpmda>
>
> (this is with /var/tmp/mmv/test as created by pcpqa/src-oss/mmv_genstats)
>
> Any ideas? Is there meant to be an initial pmid lookup in the fetch case
> in dbpmda or is the above behaviour as-expected?
>
> thanks!
>
|