----- "Paul Cowan" <cowan@xxxxxxxxxx> wrote:
> PcpMmvWriter bridge = new PcpMmvWriter(
> new File("/var/tmp/mmv/mmvtest"));
You might want to hide the "/var/tmp/" part of that, as the
pathname will need to be different on different platforms.
PCP has a (C) API interface - pmGetConfig(3) - which uses
/etc/pcp.conf to determine the PCP_TMP_DIR location (which
can be changed at runtime and which differs for different
platforms, esp. Win32).
In fact, probably don't want to expose the path separator
there at all either, as Windows blazes its own trail there
too of course.
The "mmv" part of the path needs to match with the first
part of the metric name - if its "mmv", they'll all be mmv.
prefixed (and if its "aconex" or "viewer", they'll all be
similarly prefixed automatically by the PMDA)... so might
want to abstract that part out too and allow it to be set
in just one place?
> // Automatically uses default int handler
> bridge.addMetric(
> MetricName.parse("sheep[baabaablack].bagsfull.count"), 3);
A metric specification like sheep.bagfsull.count[baabaablack]
would match up with the PCP tools like pmdumptext use, and may
make things a bit more consistent between each side of the
bridge? I'm assuming "baabaablack" is an instance name here,
or did I miss something there?
> ...
> "... preparations containing dextromethorphan are legal to
> purchase
> from most pharmacies worldwide ... [it] was specifically excluded
> from the Single Convention on Narcotic Drugs.".
>
> In other words, it's a lightweight, more accessible,
> easier-to-get-into 'bridge' to PCP. Ahem. :)
Heh ... thats funny on so many levels.
cheers.
--
Nathan
|