From 4ac9dc4d0ecdf40acaf60f3c997283178dacf574 Mon Sep 17 00:00:00 2001
From: Michael Boniface <mjb@it-innovation.soton.ac.uk>
Date: Mon, 18 Dec 2017 14:13:37 +0000
Subject: [PATCH] Update monitoring.md

---
 docs/monitoring.md | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/docs/monitoring.md b/docs/monitoring.md
index 4924b22..48ac8ad 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -2,9 +2,9 @@
 
 This document describe the low-level monitoring specification for cross-layer management and control within the FLAME platform.
 
-###Principles
+### Principles
 
-####Measurements Model
+#### Measurements Model
 
 The measurement model is based on a time-series model using the TICK stack from influxdata
 
@@ -23,9 +23,9 @@ InfluxDB is schemaless allowing arbirtary series to be stored, for example, allo
 
 Tags can be structured to provide query by dimensions allowing series data to be diced and sliced. The tags are automatically indexed.
 
-####Temporal Measurements
+#### Temporal Measurements
 
-####Spatial Measurements
+#### Spatial Measurements
 
 Discuss hierarchical tags vs GPS coordinate systems
 
@@ -35,9 +35,7 @@ The high-level entities involved in the measurement model are defined in the fig
 
 Network and host measurements are general to all surrogate SFs running within the platform. SF usage and perf measurements are specific to the SF implementation. The Platform itself is realised using SFs and therefore NAPs and the Topology Manager are also monitored using the same model. For media component SFs that form part of a Service Function Chain within a Media Service, the measurement fields are not defined and developers can decide what fields they want to use. However, global tags will be inserted for all measurements to allow for integration of SF specific measurements with network and host measurements.
 
- 
-
-###Architecture
+### Architecture
 
 Agent-based monitoring
 
-- 
GitLab