Hi, Dave -
Below is the pmwebd patch we were talking about the other day, which
provides another way to enjoy the benefits of your work-in-progress.
(It's harmless to current pcp, so it could be merged even before your
new stuff is ready.)
commit 53d34c3d7102043b66dd337a8a8fe89cd55b3518 (pcpfans.git)
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Thu Apr 23 18:34:00 2015 -0400
pmwebd: add -I option for opening directories-as-archives for graphite
This facility allows pmwebd to present to graphite-api clients such as
the graphite and grafana webapps a more compact metric-name for the
canonical sort of pmlogger directory layout, wherein each directory
that contains archives are all from the same host. The moment
pmNewContext (PM_CONTEXT_ARCHIVE, "/path/to/directory") facility
comes online, this option will let pmwebd exploit it.
The effect will be to go from having a gajillion:
[...]
pmmgr-2F-easy-2E-elastic-2E-org-2F-archive-2D-20150131-2E-110904-2E-meta.kernel.all.nprocs
pmmgr-2F-easy-2E-elastic-2E-org-2F-archive-2D-20150131-2E-110904-2E-meta.kernel.all.nprocs
pmmgr-2F-easy-2E-elastic-2E-org-2F-archive-2D-20150131-2E-110904-2E-meta.kernel.all.nprocs
pmmgr-2F-easy-2E-elastic-2E-org-2F-archive-2D-20150201-2E-110705-2E-meta.kernel.all.nprocs
[...]
items to a single:
pmmgr-2F-easy-2E-elastic-2E-org.kernel.all.nprocs
Documentation is included. Hand-QA'd via gdb (to check that
pmNewContext was being properly called on directories too). The code
is harmless to current libpcp users, even if the non-default -I flag
were turned on; updated QA asserts this. (qa/661.out may vary once
the new pmNewContext facility comes online.)
|