diff --git a/docs/monitoring.md b/docs/monitoring.md index 19bd2e4338f4ac6c982a0cb8918f9ac5cd7ec9b5..7f996042786020d64066c8010dd028096f23b190 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -43,7 +43,7 @@ Performance metrics: * response time * etc. -#### Measurements Principles and Model +#### Measurements Model ##### General @@ -66,7 +66,7 @@ https://docs.influxdata.com/influxdb/v1.4/concepts/schema_and_data_layout/ Monitoring data must have time-stamp values that are consistent and sycnrhonised across the platform. This means that all VMs hosting SFs should have a synchronised system clock, or at least (and more likely) a means by which an millisecond offset from the local time can be retrieved so that a 'platform-correct' time value can be calculated. -Integrating temporal measurements +Describe approaches to integrate temporal measurements, time as a primary key, etc. ##### Spatial Measurements @@ -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.