Hi,
On 2015-10-30 17:31, Frank Ch. Eigler wrote:
> nathans wrote:
>
>> [...] As we discussed on IRC, that is at a much lower level than is
>> relevant at this stage of evolution of a generic reporting API -
>> if/when another new fetchgroup API comes along, it will be required
>> to sit below these higher level APIs to prove its worth. [...]
>
> The fetchgroup widgets will get a reasonably high-level pmapi.py
> representation.
to me it almost looks like we already have enough such API user
candidates without pmrep (and actually it might be better to start with
them rather than with pmrep). If we want the various similar sort Python
tools to use the same higher-level metrics API (and perhaps also a
config API), pcp2graphite and pcp2elasticsearch could be converted
first, also the current pmrep's CSV and Zabbix outputs would be very
similar. I'd expect the upcoming pcp2hawkular being in this category as
well. However, pmrep's archive and stdout outputs have some
peculiarities which might then provide a use case on how to use the
generic APIs with custom properties in play (like field width, decimal
count, header printing, etc, all irrelevant for pcp2graphite and such).
Thanks,
--
Marko Myllynen
|