- building on module4, lab 2

Author: bowler

docs/class1/module4/images/api_detection_dashboard.png

@@ -1,16 +1,19 @@
 .. _LADT - Grafana Instance Access:
 
-Accessing the F5 LADT Instance
-==============================
+Accessing the F5 LADT Instance Dashboards
+=========================================
 
-We've pre-provisioned an instance of F5 LADT in the UDF lab environment. If you're ready to dive in, follow the instructions below!
+We've pre-provisioned an instance of F5 LADT in the UDF lab environment. It's ready for you to dive in and take a look. Just follow the instructions below!
+
+Accessing F5 LADT Grafana Instance
+----------------------------------
 
 #. From within the UDF course deployment's **LADT** System, locate and select **ACCESS**, then **Grafana**.
 
-    .. image:: images/udf_selfinstall_grafana_access.png
+    .. image:: images/udf_ladt_grafana_access.png
         :width: 800
 
-#. Once the new browser tab has loaded, you will be presented with the self-installed AST Grafana login. Enter the following credentials and select **Log in**.
+#. Once the new browser tab has loaded, you will be presented with the self-installed F5 LADT Grafana login. Enter the following credentials and select **Log in**.
 
     Username
 
@@ -27,3 +30,47 @@ We've pre-provisioned an instance of F5 LADT in the UDF lab environment. If you'
     .. image:: ../module2/images/grafana_login.png
         :width: 800
 
+#. You'll be presented with the Grafana homepage. From here, select the hamburger menu next to **Home** in the upper left corner, then **Dashboards**
+
+    .. image:: images/ladt_grafana_home.png
+        :width: 800
+
+#. Once the Dashboards page has loaded, you can either expand the list of dashboards by selecting the **>** symbol next to **Local API Discovery** or selecting the **Local API Discovery** folder itself.
+
+    .. image:: images/ladt_dashboards.png
+        :width: 800
+
+API Detection Dashboard
+-----------------------
+
+#. The **API Detection Dashboard** has three sections, as outlined below. Contract the *System Overview* and *System State Detail* sections by selecting the **v** next to each section title, as we're more interested in the *Detection Results*.
+
+    * System Overview
+     * Clickhouse Service Status
+     * OTel Service Status
+     * Log Analyzer Status
+     * Last Analysis Time
+     * Logs Analyzed Last Time
+     * New Logs Since Last Analysis
+    - System State Detail
+     - Analysis Settings
+     - Logs Last Processed by Host
+     - Logs Received
+     - Logs Processed at Last Analysis
+     - Last Analysis Duration
+     - CPU Utilization
+     - Memory Usage
+    - Detection Results
+     - Application Name
+     - HTTP Method
+     - Path
+     - Authentication Detected
+     - Sensitive Headers Present
+     - Sensitive Body Present
+     - Sensitive Data Types
+     - # of Requests
+
+    .. image:: images/api_detection_dashboard.png
+        :width: 800
+    
+    As detailed above, **Detection Results** is where all of the API endpoints and their detected properties will be listed. Straight away, you will be able to get a view of the number of requests an API resource has seen for a given method and whether or not sensitive data or headers have been detected.