I'm pretty sure I could count the number of people who ever used this feature on one hand. Some years ago we disabled it (service avertisement) by default in pmcd and pmproxy configs, and noone batted an eye. Unfortunately it adds build complexity, security risk, unwanted runtime dependencies on core PCP (linked into libpcp), additional systemd service dependencies, and of course a number of QA tests and common code to check it (long since untended).
I'm pretty sure I could count the number of people who ever used this feature on one hand. Some years ago we disabled it (service avertisement) by default in pmcd and pmproxy configs, and noone batted an eye. Unfortunately it adds build complexity, security risk, unwanted runtime dependencies on core PCP (linked into libpcp), additional systemd service dependencies, and of course a number of QA tests and common code to check it (long since untended).