Q: How do I integrate a local monitoring script (e.g., examples/local/example.wire) working with the mgmtui? A: Put your local monitoring script in /etc/awared/customizations.wire and it will be 'include'd into the generated wire file that the mgmtui creates. One very important point is the use of 'source:' keyword in events. This allows the mgmtui to associate the event with a node. See examples/local/example.wire for working code that does this. Q: How to get remote (i.e., 'slave') aware agents that monitor local disk, processes, etc. to have their messages appear in the web based mgmtui on a central (i.e., 'master') server? A: Follow these steps: 1) Setup the mgmtui on the 'master' machine. Confirm it is working properly. 2) Create your wire scripts for each local type of machine. Keep sure you tag all generated events using the 'source:' keyword with a value of $HOSTNAME and send them back to the machine with the mgmtui using an 'eventtx' handler. See examples/local/example.wire for working code that does this. 3) Put these scripts in /etc/awared/docroot/slaves on the 'master' machine. You can manage all these scripts from the master. The slaves will sync with the master 'awared' process to get the latest wire file. You DO NOT need to keep a seperate wire file on each slave. The idea is that you centrally manage all your monitoring configrations. 4) Install aware on the remote 'slave' machine, selecting 'slave' mode and picking the filename of the wire script you would like to run on that 'slave' machine from the set of files in the 'master's slaves directory. 5) Test it works by causing an alert on the slave machine. For example, if you are watching /etc/passwd, then do a 'touch /etc/passwd'. If the 'master' is receiving your events then you should see a log entry in /etc/awared/docroot/log/awared.log . If you set 'source:' keyword such that it matchs the node name, then you should see an event associated with that node in the mgmtui.