----- Original Message -----
> G'day Marko.
>
> On 06/05/15 19:54, Marko Myllynen wrote:
> > ...
> > right, I was blissfully unaware of this.
>
> I suspect that might be a common occurrence ... not sure how/where we need to
> advertise the derived metrics capabilities so they are more visible and the
> degree of blissful unawareness is reduced for the wider audience.
>
> Suggestions would be most welcome here.
A few possibilities spring to mind ...
- presenting some pmchart UI for adding new derivations interactively
(may need a parser-helper routine for this that pmchart can use to
give feedback about parsing error locations),
- provide a mechanism to persist derivations (in ~/.pcp/ &| /etc/pcp)
and make libpcp automatically load those metrics so that all client
tools see 'em immediately (without env vars, etc).
- as we find useful, general derivations we could install them below
/etc/pcp (ie as part of the package installation) so they're always
automatically available
>
> > I don't see Perl bindings for this, not sure is that a biggie. ...
>
> The Python bindings are probably there by accident (no Python code appears to
> be using them). Perl bindings would be simple to add if the need arose.
There are no general PMAPI perl client bindings (only the PMDA APIs).
cheers.
--
Nathan
|