diff --git a/docs/TestScenarios.md b/docs/TestScenarios.md
index 3a9013b1ea2d9337539f7ce21c7805fb905fe205..7792961147de3cbaab1fc82bdb7fbe9ced2db614 100644
--- a/docs/TestScenarios.md
+++ b/docs/TestScenarios.md
@@ -5,40 +5,41 @@
 |Rowan Powell|
 
 
-## Influx DB information
-
-client request data is going into the ```request``` table e.g. the command 
-```influx -database='testDB' -execute='SELECT * FROM request LIMIT 3'```
-gives the following response;
-```
-name: request
-time                cid                                    index                                quality segment sid
-----                ---                                    -----                                ------- ------- ---
-1515150959685000000 "13b1ddf5-578f-4cb8-914b-36f7253d485c" 63488dcb-549f-4a5d-9554-f74b381a20b4 7       1       "f79fab26-                                    c571-4d4b-aadf-747ff1c944a1"
-```
-the server response data is going into ```response``` table so typing;
-```influx -database='testDB' -execute='SELECT * FROM response LIMIT 3'```
-gives
-```
-name: response
-time                cpuUsage index                                quality qualityDifference requestID
-----                -------- -----                                ------- ----------------- ---------
-1515150959854000000 6        f449391a-e26e-440b-8498-44b1ec793961 7       0                 63488dcb-549f-4a5d-9554-f74b381a20b4
-1515150964848000000 15       123fff33-8982-4888-b0ee-846f72410db9 7       0                 d0bf70bf-2adc-4758-83a7-2a04c7ec414f
-1515150969836000000 7        35b72e5a-b176-4b06-8435-a1fb455753a7 7       0                 8f6e1743-1c00-45f4-bf71-bca9ccc8c83a
-```
+## Useful InfluxDB commands 
+
+| Action | Command example |
+| ------ | --------------- |
+| get top 3 entries from a database testDB | ```influx -database='testDB' -execute='SELECT * FROM response LIMIT 3'``` |
+| show all metrics for a database | ```influx -execute 'SHOW MEASUREMENTS ON testDB'``` |
+| show all databases | ```inflix -execute 'SHOW DATABASES'``` |
+
 
 
 ## Scenario 1 - Linear user load increase
 
+
 Simulating data from during normal usage (Users already present) and linearly increasing users
 
 * Starting at 20 users and scaling up to 40 over the time period
 * X% users using HD v Y% using SD
 * A% using resource scream, B% using LegoStarWars
 
-
-
-| Metrics | Relationships |
-| ------- | ------------- |
-| 
\ No newline at end of file
+| Data | Database |
+| ---- | -------- |
+| Client requests | request |
+| Server responses | response |
+| server VM network performance | network |
+| mpeg_dash reports | mpegdash_service |
+| server configuration events | host_resources |
+| VM state events | vm_res_alloc |
+
+
+This table is written in shorthand
+* ~: proportional to
+* #: number of
+
+| Measurement | Field | Relationships |
+| ----------- | ----- | ------------- |
+| response | cpuUsage | ~#clients |
+| SF | avg_response_time | ~#requests and ~quality |
+| SF | peak_repsonse_time | ~#requests and ~quality |