separate webfront

[Tom Nail]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Donnell Lewis wrote:
> Or you could use the distributed monitoring method:
> 
> have a master nagios server (running the web front-end) running at one
> locationa and then have another (or multiple) nagios daemons running on
> the other boxes that actually check the local machines at that colo and
> send passive check results via nsca to the master hosting the frontend.
> 
> -Don

You shouldn't even have to be that elaborate, just use an external web
server as a proxy (using mod_rewrite and mod_proxy) and restrict things
at the external portal (i.e., no commands, namespace exclusions, etc.).

Cheers,

- -=Tom Nail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHC8FF1zsLRjt/NQ0RAk/zAJwPzYz6k+VyejM8qvD3+56ToI6w1ACfVnS8
1CS0HfTNcCWwku9Vro28Q/U=
=7ArF
-----END PGP SIGNATURE-----



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null