Changes between Version 6 and Version 7 of OperationalMonitoring/DatastorePolling
- Timestamp:
- 02/17/14 16:44:43 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OperationalMonitoring/DatastorePolling
v6 v7 1 Datastore polling approach2 1 3 2 = Proposed API to poll local datastores for monitoring data = … … 9 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: 10 9 11 {{{ 12 #!html 10 * Polls are done from the Aggregator to the Local datastore via a REST API which returns JSON text. All JSON text is 13 11 14 <table border="0" style="float:center"> 15 <tr> 16 <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/DatastorePolling/aggregator_local_datastore_overview.png?format=raw" width="500" height="317"> </td> 17 </tr> 18 <caption align="bottom"> <b> Architectural Highlight of an Aggregator and a Local Datastore </b></caption> 19 </table> 20 }}} 12 * First, the Aggregator 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. 21 13 22 {{{ 23 #!html 14 * Second, the Aggregator 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. 24 15 25 <table border="0" style="float:center"> 26 <tr> 27 <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/DatastorePolling/monitoring_architecture.png?format=raw" width="500" height="317"> </td> 28 </tr> 29 <caption align="bottom"> <b> Monitoring Architecture </b></caption> 30 </table> 31 }}} 16 == Info Queries == 32 17 18 The aggregator 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 aggregator 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]. 33 19 34 This API is component (c) of the [http://www.gpolab.bbn.com/monitoring/components/ component diagram]. 35 36 37 38 * Polls are done via a REST API which returns JSON text of the queried data. See [http://rest.elkstein.org/ REST Overview] for a nice introduction to REST, and [http://www.w3schools.com/json/json_intro.asp JSON Overview] for nice introduction to JSON. 39 40 * The Aggregator 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. 41 42 * The Aggregator 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. 43 44 == Datastore/JSON Schema == 20 The aggregator 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]. 45 21 46 22 The REST noun and JSON format include the following: … … 117 93 118 94 The reference prototype will be made available soon (said 1/30/2014). 95 96 97 == Additional Resources == 98 See [http://rest.elkstein.org/ REST Overview] for a nice introduction to REST, and [http://www.w3schools.com/json/json_intro.asp JSON Overview] for nice introduction to JSON.
