----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:
> The first time a pmid appears in a pmFetch, pmlogger calls pmNameAll
> to get all of the names of the metric from the pmns to build the pmns
> fragment in the archive ... at this point the only name that can be
> found for pmid 2.4.1 is pmcd.agent.status, because the other "name"
> is not really in the pmns that is available to pmcd, and is not even
> "owned" by the PMDA with domain 2.
>
> I don't see a simple way to prevent this happening ...
How's this patch look? It has the added bonus that it removes two
round trip PDUs per metric logged (hmmmm ... wonder if this is why
some of my remote loggers take so long to start!). The main open
question is whether the (existing) task cache is ever invalid at
the time that initial callback happens... there's some hairy code
in there, but fortunately the guy who wrote it is right here. :)
$ cat tmp/config
log advisory on 1sec {
sample.secret.foo.bar.max.redirect
}
$ pminfo -a tmp/archive
sample.secret.foo.bar.max.redirect
pmcd.pmlogger.archive
pmcd.pmlogger.port
pmcd.pmlogger.host
$
Thoughts? Seems like its much improved this way, I'm wondering why
it wasn't done like this before!? (IOW, what am I missing?)
cheers.
--
Nathan
pmlogger.patch
Description: Text Data
|