[noctool-cvs] CVS web

[imattsson]

Update of /project/noctool/cvsroot/web
In directory clnet:/tmp/cvs-serv26833

Modified Files:
	hacking.html 
Log Message:
IM

Added description of default monitors (not entirely clear, unfortunately).


--- /project/noctool/cvsroot/web/hacking.html	2008/05/14 20:27:41	1.2
+++ /project/noctool/cvsroot/web/hacking.html	2008/05/17 11:25:29	1.3
@@ -42,7 +42,7 @@
  <dd>Return the next time-slot and remove it from the scheduler.
 </dl>
 
-<h2>Equipment, monitors and graphs</h2>
+<h2>Equipment</h2>
 
 Two important concepts in NOCtool are "equipment" and
 "monitors". Essentially, each "equipment" represents a physical
@@ -62,12 +62,14 @@
 Each equipment class can have 0 or more default monitors associated
 with it. There's a mapping from the equipment class to a list of
 monitors that should always exist for that equipment class.
-<p>
+
+<h2>Monitors</h2>
 Monitors can either be graphing or non-graphing. Only graphing monitor
 keep any historical state (beyond "what is my current alert
 level"). There's several types of built-in graphin classes, depending
 on the expected characteristics of the data the monitor retrieves.
-<p>
+
+<h2>Graphs</h2>
 The graph classes come in several sub-classes, depending on how they
 transfer data fromshorter-term storage to longer-term storage. Each
 storage class keeps 300 records and every 12th value added to a
@@ -115,5 +117,15 @@
 <p>
 All config files are loaded in a scrap package.
 
+<h2>Default monitors</h2>
+
+Each equipment class has a set of default monitors. The mapping from
+equipment class to monitor classes is held in *MONITOR-MAP* and
+they're instanciated by a call to DEFAULT-MONITORS. All default
+monitors that have been identified for the equipment clas and its
+super-class list are created and pushed onto the MONITORS slot of the
+equipment object (UNLESS there's already a monitor of that class in
+the list held in that slot).
+
 </body>
 </html>