| 126 | Once some measurements are 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. Now, lets step through the process of gathering memory usage data. |
| 127 | |
| 128 | Navigate to {{{ http://pcvm2-4.instageni.illinois.edu:42424/api/metadata }}} to see a list of all metadata. |
| 129 | |
| 130 | Search for "memory" and you will see every event types such as: [[BR]] |
| 131 | "ps:tools:blipp:linux:memory:utilization:free" [[BR]] |
| 132 | "ps:tools:blipp:linux:memory:utilization:kernel" [[BR]] |
| 133 | "ps:tools:blipp:linux:memory:utilization:used" |
| 134 | |
| 135 | For the memory free event type copy the value for the id key and add that value to your route, {{{ http://pcvm2-4.instageni.illinois.edu:42424/api/metadata/53a486ad377f972d2e1b8e7b }}}. This will display the single metadata object for memory free. To see the actual memory free data alter the URL to, {{{ http://pcvm2-4.instageni.illinois.edu:42424/api/data/53a486ad377f972d2e1b8e7b }}}. |
| 136 | |
| 137 | Now you should 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. |
| 138 | |
| 139 | Once you have your data you might like to visualize it to help make discoveries from the data. At this repository, [https://github.com/periscope-ps/peri-client-scripts] we provide some scripts to help you with data visualization. |
| 140 | |