>>>>> "nscott" == Nathan Scott <nscott@xxxxxxxxxx> writes:
nscott> Hi (ghost of?) Max,
nscott> No, not sure that will help - PM_TYPE_NOSUPPORT is -1, which
nscott> will trip the less-than-zero guard on the fetchCallback call
nscott> in libpcp_pmda, and that will end up in the same fprintf.
No. The idea here is to cut all calls to pmdaFetch for the metric you
don't support. First of all, if a metric is "intermittent" then you
have an option to return empty pmResult from the fetch - this is a
valid response. But if you're sure that metric is not going to be
available at all then either return error from pmLookupDesc to stop
clients from calling you or give them a descriptor with NO_SUPPORT
type and that should stop them too.
PS. I wonder what would it take to make pcp@xxxxxxxxxxx a