We have a 28 node environment where is node has PCP metrics send to a central server.
When I run the graphite emulation service for PCP archives and create a Grafana v4 data source for that instance, I find that it takes many minutes for the metrics selection widget to populate the available metrics.
This renders the integration unusable at this small scale.
Please consider taking a look at the version of pmwebd in this COPR. It aims to address this and related problems.
(In reply to Frank Ch. Eigler from comment #3)
> Please consider taking a look at the version of pmwebd in this COPR. It
> aims to address this and related problems.
Would you have information available about the changes included? It would be nice to have some information available how to use the packages, knowing the changes implemented and if there is any difference in the usage.
> > https://copr.fedorainfracloud.org/coprs/fche/pcp/
> Would you have information available about the changes included?
Certainly. The build comes from git://sourceware.org/git/pcpfans.git branch fche/pmfuntools, which is regularly rebased on top of pcp master, as long as we have features that have not yet been merged upstream.
The big ticket item is "pmwebd -J", a new default option that dramatically speeds up pmwebd when processing graphite queries against a potentially huge set of archives, and allows representation of a barely-mangled hostname (instead of a highly mangled archive path name) as the first component of the graphite metrics.
From [man pmwebd]:
-J When constructing graphite metric names, use the stored hostname instead of a archive pathname as the first component. This virtually unifies all archives found with the same hostname into a single time series. The host name is canonicalized: any symbol characters other than _ (underscore), space, - (hyphen), and / (slash) are replaced by _ (underscore).
Created attachment 1408516 [details]
Verified with pcp-3.12.2-5.el7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.