Currently, pmrep and other pcp2xxx tools can parse and use the same config files, the tools will ignore irrelevant/unsuppoted config options.
It looks like pcp2arrow is the only exception which can't be used this way. For example, one could use the same config file to display certain metrics live on a system with pmrep and then the same config file with pcp2arrow send them forward.
It could be helpful to tweak pcp2arrow also to support shared config files with pmrep, like pcp2xxx tools do. Thanks.
Currently, pmrep and other pcp2xxx tools can parse and use the same config files, the tools will ignore irrelevant/unsuppoted config options.
It looks like pcp2arrow is the only exception which can't be used this way. For example, one could use the same config file to display certain metrics live on a system with pmrep and then the same config file with pcp2arrow send them forward.
It could be helpful to tweak pcp2arrow also to support shared config files with pmrep, like pcp2xxx tools do. Thanks.