Hi Ken,
Just came across an issue when using the "magic-dynamic-namespace
name:pmid-auto-remapper-thanks-max" logic. This is quite critical
for us, so I gotta get to the bottom of this one pronto - insight
of any kind would be much appreciated.
The problem can be seen as follows (obviously, in our case its our
production PMDAs and not pmdasample) ...
$ pminfo -m sample.secret.foo.bar.max.redirect pmcd.agent.status
sample.secret.foo.bar.max.redirect PMID: 2.4.1
pmcd.agent.status PMID: 2.4.1
$ cat config
log advisory on 1sec {
sample.secret.foo.bar.max.redirect
}
$ pmlogger -c config -s 10 foo
$ pminfo -a foo
pmcd.agent.status
pmcd.pmlogger.archive
pmcd.pmlogger.port
pmcd.pmlogger.host
I'm quite surprised that the name stored is "pmcd.agent.status", when
I asked for a sample metric. Its not clear how this is happening but
its a real problem (think: scripts that were working would no longer,
as soon as this moves from QA to production ... which fortunately it
has not yet).
Any clues as to how pmlogger is managing this impressive act? It must
be doing a reverse PMID to name lookup somewhere? (can we avoid that,
somehow?!?)
Many thanks!
--
Nathan
|