Changes between Version 28 and Version 29 of OperationalMonitoring/DatastorePolling

Timestamp:

05/01/14 17:23:13 (10 years ago)

Author:

rirwin@bbn.com

Comment:

--

OperationalMonitoring/DatastorePolling

@@ -8 +8 @@
 This page describes the API to be used to poll Local datastores for monitoring data.   The API will be developed with a polling mechanism first.  Overview:
 
- * Polls are done from the collector to the Local datastore via a REST API which returns JSON text.  All JSON text is 
+ * Polls are done from the collector to the Local datastore via a REST API which returns JSON text. 
 
  * 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.  
@@ -27 +27 @@
 If the collector is tracking sliver and slice info, the collector may also be directed to a slice authority local datastore, which is a different datastore than one containing shared host nodes.  Here is a [wiki:OperationalMonitoring/DataSchema#Dataaboutasliceauthority detailed example slice query], and here is a [wiki:OperationalMonitoring/DataSchema#DataaboutaGENIuser detailed example of a user query].  Both of these queries are of similar form with <datastore_url>/info/slice/<slice_id> and <datastore_url>/info/user/<user_id> respectively.
 
-As of 17-Feb, we currently do not support querying multiple objects in a single info query.  For example, <datastore_url>/info/node/ will not return all the nodes' info at that local datastore.
+The API does not support querying multiple objects in a single info query.  For example, <datastore_url>/info/node/ will not return all the nodes' info at that local datastore.
 
 == Data Queries ==