On 29/07/14 10:28, Frank Ch. Eigler wrote:
...
This is possible (and can be encoded in a backward-compatible way).
As pmwebd is a PMAPI bridge, it is both a client and a server.
Indeed, this calculation may not be too difficult to code up in this
code, benefitting as it does from C++ and readily available context
usage statistics.
I suspect the effort is comparable for options 1. and 3. and 3. seems
like 3. might be more generally useful. I'll investigate the effort
required here.
... (Just for completeness, I'd like to re-mention the
alternative of having libpcp do this, so this many individual PMAPI
clients don't have to.)
I am willing to reconsider my historical and philosophical objections here.
I think this would need to be _optional_ as there are a number of
existing clients and plenty of use cases (especially for pmlogger) where
the current semantics (no rate conversion) are preferred.
And probably needs to be a modifier to pmNewContext(), as the semantics
need to be in place before the first metadata or pmFetch PMAPI call (the
descriptors for the counter metrics need to be re-written between pmcd
and the client, for example).
|