add proxy polling restriction, allow to query "/clients/host" #178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add in the proxy part the ability to specify which networks (or servers) can request the proxy.
This allows you to define two roles:
The feature makes it possible to fill the security hole which allows in the current version two neighboring hosts, even if they cannot communicate directly, to obtain metrics from each other or the list of all hosts known by the proxy.
To enable the feature; add in the command line interface of the pushprox_proxy:
--scrape.pollers-ip 'ipV4/32,netV4#2/net,...
example: start pushproxy proxy and client on same server:
Try to scrap an exporter listening on port 9321 on same server through server ip: reply "403 Forbidden" and in body "Not an authorized poller"
try to scrap httpapi_exporter through loopback ip :
Add the feature to query if a specified fqdn can be found the the fqdn list of knwown hosts
two cases:
e.g.: poller role is not defined.
look for fqdn "localhost":
poller role is defined ( 127.0.0.1:8080 only )