Changes between Version 29 and Version 30 of OperationalMonitoring/DatastorePolling

Timestamp:

05/02/14 14:28:26 (10 years ago)

Author:

rirwin@bbn.com

Comment:

--

OperationalMonitoring/DatastorePolling

@@ -16 +16 @@
 == Info Queries ==
 
-The collector retrieves from a config local datastore (to be developed and is hardcoded for now), a set of urls of local datastores that are associated with one or more aggregate managers (AMs).  This allows the collector to poll local datastores for information about the data associated with each local datastore and AM at <datastore_url>/info/aggregate/<aggregate_id>.  The information returned is a list of properties about the aggregate as well as a list of nodes, slivers, and VLANs (slivers and VLANs not implemented as of 17-Feb).   Here is  [wiki:OperationalMonitoring/DataSchema#Dataaboutanaggregate a detailed example of an aggregate info query].
+The collector retrieves from a config local datastore (to be developed and is hardcoded for now), a set of urls of local datastores that are associated with one or more aggregate managers (AMs).  This allows the collector to poll local datastores for information about the data associated with each local datastore and AM at <datastore_url>/info/aggregate/<aggregate_id>.  The information returned is a list of properties about the aggregate as well as a list of nodes, slivers, and VLANs.   Here is  [wiki:OperationalMonitoring/DataSchema#Dataaboutanaggregate a detailed example of an aggregate info query].
 
 The collector will then query for information about particular objects one at a time (i.e., a node).  The query returns a list of properties about the object as well as a list of associated objects (i.e., a node's interfaces).  In this example, a node info query will be at <datastore_url>/info/node/<node_id>.  Here is a [wiki:OperationalMonitoring/DataSchema#Dataaboutanode a detailed example of a node info query].  The collector would repeat for other nodes it received in the list in the aggregate info query.