Hi Martins,
----- Original Message -----
> Hi,
> We ran into some issues with the perfevent pmda where since we had
> used the names that libpfm provides directly, some of these names
> contain characters that cause problems with various pcp tools. These
> include "equals", "dash" and other similar things. The pmda API doesn't
> complain about these but other parts of PCP do. Here is a first hack at
> fixing this problem (and patch attached since its small):
Nice and simple.
> https://github.com/ubccr/pcp/tree/perfevent_namechange
>
> It includes a flag to preserve the old behavior. I looked into writing
> some rules for pmlogrewrite, but didn't see a way to do wholesale regex
> type substitutions. I'm not sure if there is a way to effectively do
(yeah, I don't believe there's any such capability)
> this since there are possibly hundreds of different metrics that could
> exist depending on your architecture. The metric names are generated on
> the fly from what libpfm provides.
>
> Any thoughts on other ways to mitigate issues for others who may be
> using this pmda?
Only thought so far would be to provide a little shell script that can
produce pmlogrewrite files based on the local metrics, that people could
run & then install the config (manually) when doing the switch over. If
we place that in /var/lib/pcp/pmdas/perfevent/ (permanently) and then
document it a bit on the pmdaperfevent man page, that's probably enough?
cheers.
--
Nathan
|