<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-GB link=blue vlink=purple> <div class=Section1> Hi, I’ll start by admitting n00bness but I have googled a lot about nagios and I hope that this will not duplicate a previous mail. Be kind!<o:p></o:p> <o:p> </o:p> I am looking to create a monitoring model that does not cleanly fit into anything I have seen, and before I spend days getting it all to (not) work I wanted to validate my plans. Basically, I have a lot of remote, temporary events sites popping up on ADSL or behind multiple NATs (ie outbound access to the Internet only) and going after a few weeks. On site infrastructure will go up very quickly and come down equally quickly [1].<o:p></o:p> <o:p> </o:p> What I want to be able to do is have a layout so that:<o:p></o:p> <![if !supportLists]>- <![endif]>I can access a view of the local site devices site from a local event server and a view of all the sites from the central server<o:p></o:p> <![if !supportLists]>- <![endif]>All the polling happens from the local site servers and the central server only pings the external ADSL IPs of each site to check if they are alive<o:p></o:p> <![if !supportLists]>- <![endif]>All alerts are sent out from the central server via email, sms etc<o:p></o:p> <![if !supportLists]>- <![endif]>Most checks will just be pings or receipt of syslog/snmp traps from local devices<o:p></o:p> <o:p> </o:p> I am assuming I will need to play with NSCA and have the local server doing active checks, exporting stats to a file, and the central server doing passive checks, with NCSA syncing the stats to the central server. However, ADSL polling stats for each site need to be synced back to the local servers if they are available so the on site view shows those stats too<o:p></o:p> <o:p> </o:p> Some things I am not sure about though: a) the line above b) that this is possible with only outbound access to the Internet from the local server c) how management of configured devices is kept in sync between the local and central servers d) how the central server can have suppression/correlation of events so that a remote site being down shows just “site X down” instead of 100 alerts about each element of the site being down<o:p></o:p> <o:p> </o:p> The key part of this is that there can be really complicated parts to the setup, but the day to day operation must be as simple as possible, ie I can’t expect users to have instructions like “log into linux, use vi to change configs, kill sighup and use rsync to the manager to update it”<o:p></o:p> <o:p> </o:p> Is this just far too complicated an idea?<o:p></o:p> <o:p> </o:p> Thanks in advance<o:p></o:p> <o:p> </o:p> --Chris<o:p></o:p> <o:p> </o:p> [1] on a side note on advice on how to best to get very simple non technical users to be able write monitoring configs would be appreciated<o:p></o:p> </div> </body> </html>