Changes between Version 25 and Version 26 of GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_data/RetrieveData


Ignore:
Timestamp:
06/21/14 00:37:07 (10 years ago)
Author:
mkeele@indiana.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEMINI/Tutorial/GEC20/GENI_Desktop_and_GEMINI_data/RetrieveData

    v25 v26  
    1471471. http://pcvm2-4.instageni.illinois.edu:42424/api/measurements
    148148
    149 [[Image()]]
     149[[Image(cpu_measurement.png)]]
    150150
    151151Once some measurements have been posted and executed by BLiPP, metadata will be generated. Every measurement object has a list of event types associated with it and you will use this event type of find the data you desire. For example, if you were to schedule a throughput test you could expect an event type for bandwidth. BLiPP executes a few measurement probes directly after Instrumentation, such as cpu, mem, and net.
     
    168168  * single metadata object for load min load
    169169
    170 [[Image()]]
     170[[Image(cpu_metadata.png)]]
    171171
    172172Replace metadata with data in the URL to get the data associated with the metadata event type
     
    175175  * actual cpu load data
    176176
    177 [[Image()]]
     177[[Image(cpu_data.png)]]
    178178
    179179Now you will see all your data in JSON format. To reiterate, each metadata object represents an event type for a particular measurement. Navigating to a particular event type/metadata object by the metadata ID will get the single metadata object. Using that metadata ID, you can query the data route to get the data associated with that event type.