Changes between Version 13 and Version 14 of OperationalMonitoring/DataSchema20
- Timestamp:
- 08/28/14 11:29:07 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OperationalMonitoring/DataSchema20
v13 v14 22 22 }}} 23 23 24 <aggregate-id> is usually the aggregate's GENI-assigned nickname ( shortname).24 <aggregate-id> is usually the aggregate's GENI-assigned nickname (common name). 25 25 26 26 Example REST call for aggregate gpo-ig: … … 449 449 If <list of object ids> is "*", it means "all objects known to the datastore of type <object type name>." 450 450 451 The response is a list "[...]" in which each element conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/data data ]: dataschema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/data.schema.jwc commented version of the data schema].451 The response is a list "[...]" in which each element conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/data data schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/data.schema.jwc commented version of the data schema]. 452 452 Each element of the list applies to one (eventType, object id) pair. 453 453 … … 669 669 670 670 Retrieves a variety of configuration information, including: 671 * locations (URLs) of and information about other datastores672 * GENI authorities673 * Database schemas used to store monitoring information674 * A list of possible event types for time-series measurements671 * locations (URLs) of and information about other datastores 672 * GENI authorities 673 * Database schemas used to store monitoring information 674 * A list of possible event types for time-series measurements 675 675 676 676 Example REST call for geni-prod, a hypothetical config datastore listing production aggregates and authorities: