FOGL-9206 Correct image names (#1474)

* FOGL-9206 Correct image names Signed-off-by: Mark Riddoch <mark@dianomic.com> * Add title Signed-off-by: Mark Riddoch <mark@dianomic.com> --------- Signed-off-by: Mark Riddoch <mark@dianomic.com>
fledge-iot · Oct 22, 2024 · cea35a4 · cea35a4
1 parent abcc7e4
commit cea35a4
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 7 deletions.
diff --git a/docs/monitoring/configuration.rst b/docs/monitoring/configuration.rst
@@ -48,7 +48,7 @@ Each time any user modifies a configuration item a Slack message will be sent to
 This is a very simple message that only gives the information that a change has been made, however more sophisticated delivery mechanisms can be used that will detail the actual change.
 
 Sending To External Systems
---------------------------
+---------------------------
 
 Audit log data can also be sent to the north in the same way that reading data can. This can be used to send data to third party systems to maintain a change log of internal Fledge changes in other systems. In order to send audit log data to the north we merely setup a new north service or task. When we configure the north plugin we select the data source as *audit* rather than readings or statistics.
 

diff --git a/docs/monitoring/flow.rst b/docs/monitoring/flow.rst
@@ -1,7 +1,7 @@
-.. |MonitorNorthRate| image:: ../imagesMonitorNorthRate.jpg
-.. |MonitorZendesk| image:: ../imagesMonitorZendesk.jpg
+.. |MonitorNorthRate| image:: ../images/MonitorNorthRate.jpg
+.. |MonitorZendesk| image:: ../images/MonitorZendesk.jpg
 .. |MonitorTrigger| image:: ../images/MonitorTrigger.jpg
-.. |MonitorBuffered| image:: ../images/MonitorBuffered.jpg
+.. |MonitoredBuffered| image:: ../images/MonitoredBuffered.jpg
 
 Pipeline Data Flow
 ==================

diff --git a/docs/monitoring/introduction.rst b/docs/monitoring/introduction.rst
@@ -1,3 +1,6 @@
+Introduction
+============
+
 Monitoring within Fledge is a varied subject and has different meanings to the different user personas that are using Fledge.
 
 Monitoring can take the form of

diff --git a/docs/monitoring/resources.rst b/docs/monitoring/resources.rst
@@ -1,4 +1,4 @@
-.. |MonitorDiskUsge| image:: ../images/MonitorDiskUsge.jpg
+.. |MonitorDiskUsage| image:: ../images/MonitorDiskUsage.jpg
 
 Resources
 =========
@@ -36,9 +36,9 @@ In this example we will assume we want to use the notification service to monito
 
 Since we are looking for a numeric value to go above a certain value, say 85%, we can simply use the threshold notification rule to detect the disk usage going above this value and deliver a notification using any of the Fledge notification delivery mechanisms.
 
-+====================+
++--------------------+
 | |MonitorDiskUsage| |
-+====================+
++--------------------+
 
 Database Disk Usage
 ===================
-Original file line number
+Diff line change
@@ Expand Up @@
     This is a very simple message that only gives the information that a change has been made, however more sophisticated delivery mechanisms can be used that will detail the actual change.
     Sending To External Systems
-    --------------------------
+    ---------------------------
     Audit log data can also be sent to the north in the same way that reading data can. This can be used to send data to third party systems to maintain a change log of internal Fledge changes in other systems. In order to send audit log data to the north we merely setup a new north service or task. When we configure the north plugin we select the data source as *audit* rather than readings or statistics.
@@ Expand Down @@