You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Hi! Long time listener, first time caller. Great tool!)
For context: We monitor some of our customers' servers by installing a pushprox and a node exporter on their machine, and on our end we run a pushprox server (exposed to the internet through a reverse proxy) that can reach our internal prometheus server.
This is the use case: One of our customer's servers, in addition to not being exposed to the internet, is only able to get to the internet through a proxy, Squid I believe. Also, it is not a transparent proxy.
Is there a way for the pushprox client to explicitly specify an HTTP proxy for it to reach the outside world?
The text was updated successfully, but these errors were encountered:
(Hi! Long time listener, first time caller. Great tool!)
For context: We monitor some of our customers' servers by installing a pushprox and a node exporter on their machine, and on our end we run a pushprox server (exposed to the internet through a reverse proxy) that can reach our internal prometheus server.
This is the use case: One of our customer's servers, in addition to not being exposed to the internet, is only able to get to the internet through a proxy, Squid I believe. Also, it is not a transparent proxy.
Is there a way for the pushprox client to explicitly specify an HTTP proxy for it to reach the outside world?
The text was updated successfully, but these errors were encountered: