Changes between Version 1 and Version 2 of OperationalMonitoring/DatastorePolling20


Ignore:
Timestamp:
08/28/14 12:45:02 (10 years ago)
Author:
dwiggins@bbn.com
Comment:

url -> URL

Legend:

Unmodified
Added
Removed
Modified

  • OperationalMonitoring/DatastorePolling20

    v1 v2  
    1010 * Polls are done from the collector to the Local datastore via a REST API which returns JSON text.
    1111
    12  * First, the Collector polls a Local datastore at '/info/' of the local store url to get information about what the datastore has.  This is done through multiple polls, outlined below. 
     12 * First, the Collector polls a Local datastore at '/info/' of the local store URL to get information about what the datastore has.  This is done through multiple polls, outlined below. 
    1313
    1414 * Second, the collector polls for time-series data at '/data/' to get event-based or measurement data.  The query contains a set of event types, a set of object IDs, and timestamp filters, outlined below.
    … …  
    1616== Info Queries ==
    1717
    18 The collector retrieves from a config local datastore 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/DataSchema20#Aggregatecallandresponse a detailed example of an aggregate info query].
     18The collector retrieves from a config local datastore 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/DataSchema20#Aggregatecallandresponse a detailed example of an aggregate info query].
    1919
    2020The 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/DataSchema20#Nodecallandresponse 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.