i thought he wanted to send the monit traffic to mmonit via a http/socks5 proxy
Sent from my iPad > On 17 Dec 2013, at 11:52 PM, Martin Pala <[email protected]> wrote: > > Please can you describe what exactly do you want to monitor? Is it the proxy > itself or the remote website health? > > If you're testing via proxy and the request fails, then you cannot tell if > the problem is on the proxy itself or behind it (network, etc.), hence > testing other websites via proxy is suboptimal (due to extra indirection > level) - the only thing which you can test reliably is the proxy itself. If > you really want to make sure some site is generally available (not just via > your proxy), then you should definitely bypass the proxy and test directly. > The probe location depends what you really want to test - whether the network > or the service on the remote host itself. > > To send proxy request you can use for example generic send/request test to > ask proxy for some specific page behind it, see manual for more details: > http://www.mmonit.com/monit/documentation/monit.html#connection_testing > > The HTTP request via proxy is similar to normal request, you just need to > specify full URL in the request. > > > Regards, > Martin > > > >> On 17 Dec 2013, at 20:01, Philip Waters <[email protected]> wrote: >> >> Is monit's failure to honor system proxy for monitoring websites on the >> other side of the proxy due to specific distribution issues, or is it a >> failure of the monit software. Is there any plan to implement either a >> directive or intuition into the application that would understand system >> proxy settings? >> >> Phil >> >> -- >> To unsubscribe: >> https://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
