From 11afa3732c6156d2e5c073aa9c5af9b055b09013 Mon Sep 17 00:00:00 2001 From: Simon Crowle <sgc@it-innovation.soton.ac.uk> Date: Wed, 3 Jan 2018 09:51:31 +0000 Subject: [PATCH] Update monitoring.md --- docs/monitoring.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/monitoring.md b/docs/monitoring.md index 3995dad..7f99604 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -78,15 +78,15 @@ Tag location | --- | --- | --- | | DATACENTRE_1 | 0 | 0 | -A SF media transcoder is placed in a lamp-post. It has no means to obtain GPS coordinates but has a _loc_label_ provided to it as a VM environment variable. It provides zeros in the longitude and latitude. In subsequent data analysis we can search for this SF by location label. +A SF media transcoder is placed in a lamp-post. It has no means to obtain GPS coordinates but has a _location_label_ provided to it as a VM environment variable. It provides zeros in the longitude and latitude. In subsequent data analysis we can search for this SF by location label. GPS coordination location -| loc_label | loc_long | loc_lat | +| location_label | location_long | location_lat | | --- | --- | --- | | LAMP_1 | 50.842715 | -0.778276 | -A SF that is a proxy to a user attached to a NAP running in street lamp post LAMP_1. Here we have knowledge both of the logical location of the service and also the fine-grained, dynamic position of the service user. Lots of interesting possibilities with both of these bits of information! +A SF that is a proxy to a user attached to a NAP running in street lamp post LAMP_1. Here we have knowledge both of the logical location of the service and also the fine-grained, dynamic position of the service user. Note that tags are always strings and cannot be floats, therefore log and lat will always be stored as a measurement field. -- GitLab