Changes between Version 31 and Version 32 of OperationalMonitoring/DataSchema


Ignore:
Timestamp:
02/20/14 16:13:29 (6 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DataSchema

    v31 v32  
    6262Aggregates are indexed by GENI-agreed short name and described using [http://www.gpolab.bbn.com/monitoring/schema/20140131/aggregate# the aggregate schema].  Examples:
    6363
    64  Call for GPO-IG:
     64Hypothetical REST call for GPO-IG:
    6565{{{
    6666https://datastore.instageni.gpolab.bbn.com/aggregate/gpo-ig
     
    9797
    9898Nodes have an ID which is a URL-sanitized version of their URN and are described using [http://unis.incntre.iu.edu/schema/20120709/node# the node schema].  Examples:
    99  Call for GPO-IG PC1:
     99 Hypothetical REST call for GPO-IG PC1:
    100100{{{
    101101https://datastore.instageni.gpolab.bbn.com/node/instageni.gpolab.bbn.com_node_pc1
     
    143143Examples:
    144144
    145  Call for pc1 eth0 (control) at gpo-ig:
     145 Hypothetical REST call for pc1 eth0 (control) at gpo-ig:
    146146{{{
    147147https://datastore.instageni.gpolab.bbn.com/interface/instageni.gpolab.bbn.com_interface_pc1:eth0
     
    168168}
    169169}}}
    170  Call for pc1 eth1 (dataplane) interface at gpo-ig:
     170
     171 Hypothetical REST call for pc1 eth1 (dataplane) interface at gpo-ig:
    171172
    172173{{{
    173174https://datastore.instageni.gpolab.bbn.com/interface/instageni.gpolab.bbn.com_interface_pc1:eth1
    174175}}}
    175 
    176 
     176 Response:
    177177{{{
    178178{
     
    201201
    202202
    203  Call for authority of ch.geni.net:
     203 Hypothetical REST call for authority of ch.geni.net:
    204204{{{
    205205https://datastore.ch.geni.net/authority/ch.geni.net
     
    231231
    232232GENI users have an ID based on the username and are described using [http://www.gpolab.bbn.com/monitoring/schema/20140131/user# the GENI user schema].  Examples:
    233  * tupty at ch.geni.net:
     233
     234 Hypothetical REST call for user tupty at ch.geni.net:
     235{{{
     236 https://datastore.ch.geni.net/user/tupty
     237}}}
     238 Response:
    234239{{{
    235240{
     
    251256
    252257GENI slices have an ID based on the URN and are described using [http://www.gpolab.bbn.com/monitoring/schema/20140131/slice# the GENI slice schema].  Examples:
    253  * tuptyexclusive slice:
     258Hypothetical REST call for tuptyexclusive slice:
     259{{{
     260 https://datastore.ch.geni.net/slices/ch.geni.net_gpo-infra_slice_tuptyexclusive
     261}}}
     262
    254263{{{
    255264{
     
    279288
    280289GENI sliver have an ID based on the URN and are described using [http://www.gpolab.bbn.com/monitoring/schema/20140131/sliver# the GENI sliver schema].  Examples:
    281  * tuptyexclusive instageni sliver:
     290 Hypothetical REST call for tuptyexclusive instageni sliver:
     291{{{
     292https://datastore.instageni.gpolab.bbn.com/slivers/instageni.gpolab.bbn.com_sliver_26947
     293}}}
     294 Response:
    282295{{{
    283296{
     
    313326
    314327Measurements have an opaque ID which is generated by the local datastore which serves them, and must be persistent, so that the caller has the option of asking for the measurement by ID.  They are described using the data schema outlined above.  Examples:
    315  * CPU utilization metric on pc1:
     328Hypothetical REST call for CPU utilization metric on pc1:
     329{{{
     330https://datastore.instageni.gpolab.bbn.com/data/q?={"filters":{"eventType": ["ops_monitoring:cpu_util"],"ts":{"gte":0},"obj":{"type":"node","id":["instageni.gpolab.bbn.com_node_pc1"]}}}
     331}}}
     332Response
    316333{{{
    317334{
     
    332349}
    333350}}}
    334  * Percentage of swap available on pc1:
     351Hypothetical REST call for percentage of swap available on pc1:
     352{{{
     353https://datastore.instageni.gpolab.bbn.com/data/q?={"filters":{"eventType": ["ops_monitoring:swap_free"],"ts":{"gte":0},"obj":{"type":"node","id":["instageni.gpolab.bbn.com_node_pc1"]}}}
     354
     355}}}
     356Response:
    335357{{{
    336358{
     
    351373}
    352374}}}
    353  * Memory in active use on pc1:
     375Hypothetical REST call for memory in active use on pc1:
     376{{{
     377https://datastore.instageni.gpolab.bbn.com/data/q?={"filters":{"eventType": ["ops_monitoring:mem_active_kb"],"ts":{"gte":0},"obj":{"type":"node","id":["instageni.gpolab.bbn.com_node_pc1"]}}}
     378}}}
     379Response:
    354380{{{
    355381{
     
    370396}
    371397}}}
    372  * Bytes per second received by `pc1:eth0`:
     398 Hypothetical call for bytes per second received by `pc1:eth0`:
     399{{{
     400https://datastore.instageni.gpolab.bbn.com/data/q?={"filters":{"eventType": ["ops_monitoring:rx_bytes"],"ts":{"gte":0},"obj":{"type":"interface","id":["instageni.gpolab.bbn.com_node_pc1:eth0"]}}}
     401}}}
     402Response:
    373403{{{
    374404{
     
    389419}
    390420}}}
    391  * Boolean metric indicating whether pc1 is available for use according to the aggregate responsible for it:
     421Hypothetical REST call for boolean metric indicating whether pc1 is available for use according to the aggregate responsible for it:
     422{{{
     423https://datastore.instageni.gpolab.bbn.com/data/q?={"filters":{"eventType": ["ops_monitoring:is_available"],"ts":{"gte":0},"obj":{"type":"node","id":["instageni.gpolab.bbn.com_node_pc1"]}}}
     424}}}
     425Response:
    392426{{{
    393427{
     
    489523]
    490524}}}
    491