Hi I was wondering if somebody could help me. I have spoken to sales on the phone and they can't give me a definitive answer until the technical guy is back next week.
We are thinking of deploying Nagios at my company to monitor our windows serves. The servers are located in schools and colleges that have a government body a run proxy to access the internet. This proxy requires authentication and I was wondering if Nagios supports this. My vision is to have a Nagios server at our office which monitors the servers in the schools but obviously to make the connection there needs to be some proxy authentication in there somewhere. I have installed NSCLient++ on 1 server but I can't seem to find anywhere to input proxy credentials. Without this, the client can't talk to the server back at our office. So is it possible to have NSCLient++ or the vanilla SNMP service send information over a WAN link to Nagios?
Another possible avenue I have come across is termed 'Distributed Monitoring' which involves deploying a Nagios server at each site and have them send the data back to our Nagios main server at the office as defined in https://mail.oakforduk.com/exchweb/bin/ ... buted.html. Again, my question is it possible to input proxy authentication into Nagios so that it can send the data back to our Primary Nagios server.
Please note that using VPN connections to all of these sites is not possible.
Any help would be greatly appreciated. Many Thanks
Regards,
Gareth
Multiple site monitoring with Proxies authentication
-
tonyyarusso
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Multiple site monitoring with Proxies authentication
Not internally to Nagios XI. However, you may be able to accomplish what you need with a tool such as 'tsocks', which intercepts calls for network connections and reroutes them through a proxy.
Re: Multiple site monitoring with Proxies authentication
We don't have a product for this, but Distributed monitoring would be the solution for you. Each location has a Nagios server, this could be Nagios Core and you could get support from us for that. Then all the check results are sent, perhaps over a proxy using tsocks to a central location. This is where you'd want to have NagiosXI with all it's UI goodness.
You could also setup a NSClient++ wrapper that loads tsocks if a specific parameter is set. You can also choose to load tsocks system wide so every application will use a proxy.
If you have multiple proxy servers you would create a tsocks config file for each and have your wrapper script set TSOCKS_CONF_FILE as well as LD_PRELOAD=/lib/libtsocks.so
.
You could also setup a NSClient++ wrapper that loads tsocks if a specific parameter is set. You can also choose to load tsocks system wide so every application will use a proxy.
If you have multiple proxy servers you would create a tsocks config file for each and have your wrapper script set TSOCKS_CONF_FILE as well as LD_PRELOAD=/lib/libtsocks.so
.
Re: Multiple site monitoring with Proxies authentication
Thanks for the replies.
Hmm, I can't believe this isn't supported natively. I don't see why the data can't be sent back to a server using http and authenticating through the proxy.
How difficult is it to install and configure tsocks on my Nagios vmware appliance. Is there a guide?
Thanks for the help
Hmm, I can't believe this isn't supported natively. I don't see why the data can't be sent back to a server using http and authenticating through the proxy.
How difficult is it to install and configure tsocks on my Nagios vmware appliance. Is there a guide?
Thanks for the help
Re: Multiple site monitoring with Proxies authentication
http is a different matter, most of these checks internally support the use of most standard proxies used by web clients. It's the other checks like NSClient++ that don't internally manage proxy(s).
tsocks should be a 10 min thing, after the install you type the server name, type, and login into the config file and then set environment variables for when you'd want to use the proxy or set it globally.
tsocks should be a 10 min thing, after the install you type the server name, type, and login into the config file and then set environment variables for when you'd want to use the proxy or set it globally.