CL Doc Updates

docs/LABDCN-2620/README.md

@@ -7,7 +7,7 @@ DMZ credentials will be available from the eXpo portal.
 
 ## Task 1 - Getting Familiar with the ACI Monitoring Stack
 
-If this is your first time learning about the ACI monitoring stack you should start with the [README](../../README.md) that provides an overview of the Stack Architecture.
+If this is your first time learning about the ACI monitoring stack you should start with the [Overview](overview.md) that provides an overview of the Stack Architecture.
 You do not need to deep dive in the details, unless you want to, but is good to have a generic understanding of the components used in the Stack.
 
 Next head over the [Demo Environment](../demo-environment.md) documentation, as you read this section explore the dashboard that are available in the Demo Environment.

docs/LABDCN-2620/overview.md

@@ -0,0 +1,114 @@
+aci-monitoring-stack - Open Source Monitoring for Cisco ACI
+------------
+
+# Overview
+
+Harness the power of open source to efficiently monitor your Cisco ACI environment with the ACI-Monitoring-Stack. This lightweight, yet robust, monitoring solution combines top-tier open source tools, each contributing unique capabilities to ensure comprehensive visibility into your ACI infrastructure.
+
+The ACI-Monitoring-Stack integrates the following key components:
+
+- [Grafana](https://grafana.com/oss/grafana/): The leading open-source analytics and visualization platform. Grafana allows you to create dynamic dashboards that provide real-time insights into your network's performance, health, and metrics. With its user-friendly interface, you can easily visualize and correlate data across your ACI fabric, enabling quicker diagnostics and informed decision-making.
+
+- [Prometheus](https://prometheus.io/): A powerful open-source monitoring and alerting toolkit. Prometheus excels in collecting and storing metrics in a time-series database, allowing for flexible queries and real-time alerting. Its seamless integration with Grafana ensures that your monitoring stack provides a detailed and up-to-date view of your ACI environment.
+
+- [Loki](https://grafana.com/oss/loki/): Designed for efficiently aggregating and querying logs from your entire ACI ecosystem. Loki complements Prometheus by focusing on log aggregation, providing a unified stack for metrics and logs. Its integration with Grafana enables you to correlate log data with metrics and create a holistic monitoring experience.
+
+- [Promtail](https://grafana.com/docs/loki/latest/send-data/promtail/): the agent responsible for gathering and shipping the log files to the Loki server.
+
+- [Syslog-ng](https://github.com/syslog-ng/syslog-ng): is an open-source implementation of the Syslog protocol, its role in this stack is to translate syslog messages from RFC 3164 to 5424. This is needed because Promtail only support Syslog RFC 5424 over TCP and this capability is only available in ACI 6.1 and above.
+
+- [aci-exporter](https://github.com/opsdis/aci-exporter): A Prometheus exporter that serves as the bridge between your Cisco ACI environment and the Prometheus monitoring ecosystem. The aci-exporter translates ACI-specific metrics into a format that Prometheus can ingest, ensuring that all crucial data points are captured and monitored effectively.
+
+- Pre-configured ACI data collections queries, alerts, and dashboards (Work In Progress): The ACI-Monitoring-Stack provides a solid foundation for monitoring an ACI fabric with its pre-defined queries, dashboards, and alerts. While these tools are crafted based on best practices to offer immediate insights into network performance, they are not exhaustive. The strength of the ACI-Monitoring-Stack lies in its community-driven approach. Users are invited to contribute their expertise by providing feedback, sharing custom solutions, and helping enhance the stack. Your input helps to refine and expand the stack's capabilities, ensuring it remains a relevant and powerful tool for network monitoring.
+
+# Your Stack
+
+To gain a comprehensive understanding of the ACI Monitoring Stack and its components it is helpful to break down the stack into separate functions. Each function focuses on a different aspect of monitoring the Cisco Application Centric Infrastructure (ACI) environment.
+
+## Fabric Discovery:
+
+The ACI monitoring stack uses Prometheus Service Discovery (HTTP SD) to dynamically discover and scrape targets by periodically querying a specified HTTP endpoint for a list of target configurations in JSON format.
+
+The ACI Monitoring Stack needs only the IP addresses of the APICs, the Switches will be Auto Discovered. If switches are added or removed from the fabric no action is required from the end user.
+
+```mermaid
+    flowchart-elk RL
+      P[("Prometheus")]
+      A["aci-exporter"]
+      APIC["APIC"]
+
+      APIC -- "API Query" --> A
+      A -- "HTTP SD" --> P
+```
+
+## ACI Object Scraping: 
+
+`Prometheus` scraping is the process by which `Prometheus` periodically collects metrics data by sending HTTP requests to predefined endpoints on monitored targets. The `aci-exporter` translates ACI-specific metrics into a format that `Prometheus` can ingest, ensuring that all crucial data points are captured and monitored effectively.
+
+```mermaid
+    flowchart-elk RL
+      P[("Prometheus")]
+      A["aci-exporter"]
+      subgraph ACI
+        S["Switches"]
+        APIC["APIC"]
+      end
+      A--"Scraping"-->P
+      S--"API Queries"-->A
+      APIC--"API Queries"-->A
+```
+## Syslog Ingestion:
+
+The syslog config is composed of 3 components: `promtail`, `loki` and `syslog-ng`.
+Prior to ACI 6.1 `syslog-ng` is required between `ACI` and `Promtail` to convert from RFC 3164 to 5424 syslog message format.
+
+```mermaid
+    flowchart-elk LR
+      L["Loki"]
+      PT["Promtail"]
+      SL["Syslog-ng"]
+      PT-->L
+      SL-->PT
+      subgraph ACI
+        S["Switches"]
+        APIC["APIC"]
+      end
+      V{Ver >= 6.1}
+      S--"Syslog"-->V
+      APIC--"Syslog"-->V
+      V -->|Yes| PT
+      V -->|No| SL
+```
+
+## Data Visualization
+
+The Data Visualization is handled by `Grafana`, an open-source analytics and monitoring platform that allows users to visualize, query, and analyze data from various sources through customizable and interactive dashboards. It supports a wide range of data sources, including `Prometheus` and `Loki` enabling users to create real-time visualizations, alerts, and reports to monitor system performance and gain actionable insights.
+
+```mermaid
+    flowchart-elk RL
+      G["Grafana"]
+      L["Loki"]
+      P[("Prometheus")]
+      U["User"]
+
+      P--"PromQL"-->G
+      L--"LogQL"-->G
+      G-->U
+```
+## Alerting
+
+`Alertmanager` is a component of the `Prometheus` ecosystem designed to handle alerts generated by `Prometheus`. It manages the entire lifecycle of alerts, including deduplication, grouping, silencing, and routing notifications to various communication channels like email, `Webex`, `Slack`, and others, ensuring that alerts are delivered to the right people in a timely and organized manner.
+
+In the ACI Monitoring Stack both `Prometheus` and `Loki` are configured with alerting rules.
+```mermaid
+flowchart-elk LR
+  L["Loki"]
+  P["Prometheus"]
+  AM["Alertmanager"]
+  N["Notifications (Mail/Webex etc...)"]
+  L --> AM
+  P --> AM 
+  AM --> N
+```
+
+[Back](README.md)

docs/demo-environment.md

@@ -11,14 +11,31 @@ The guest user is able to modify the dashboards and run `Explore` queries howeve
 
 # Exploring the ACI Monitoring Stack
 
-In this section I am gonna guide you trough the available dashboards and how to use them.
+In this section I am going to guide you trough the available already built dashboards and how to use them. We will cover two types of dashboards based on data provided by Prometheus for fault and alerts data and Loki for syslog data. 
 
 *Note:* Grafana support building dashboard with data coming from Multiple data source but for the moment, the ACI Monitoring stack does not make use of such capability. 
 
 All the Dashboards are located in the `ACI` Folder in the `Dashboards` section of the UI:
 ![dashboards](images/dashboards.png)
 
 
+The stack is pre-provisioned with the following Dashboards. Feel free to explore the ones that are of interest.
+<!-- no toc -->
+- [Prometheus backed Dashboards](#prometheus-backed-dashboards)
+  - [ACI Faults](#aci-faults)
+  - [EPG Explore](#epg-explore)
+  - [EPG Stats](#epg-stats)
+  - [Fabric Capacity](#fabric-capacity)
+  - [Node Capacity](#node-capacity)
+  - [Node Details](#node-details)
+  - [Nodes Interfaces](#nodes-interfaces)
+  - [Power Usage](#power-usage)
+  - [Routing Protocols](#routing-protocols)
+  - [Vlans](#vlans)
+- [Loki backed Dashboards](#loki-backed-dashboards)
+  - [Contract Drops Logs](#contract-drops-logs)
+
+
 ## Prometheus backed Dashboards
 
 These dashboards are using `Prometheus` as data source meaning the data we are visualizing came from an ACI Managed Object and was translated by the `aci-exporter`
@@ -111,4 +128,4 @@ These dashboards are using `Loki` as data source meaning the data we are visuali
 
 This dashboard parses the logs received by the switches and extract infos on the Contract Drop Logs. This requires a specific [config](syslog.md) on ACI and is limited to 500 Messages/s per switch
 
-
+[Next - Lab1](labs/lab1.md)

docs/labs/lab2.md

@@ -74,4 +74,4 @@ The result will be something similar to what you can see below, feel free to use
 ![alt text](images/lab2/ui-filter-result.png)
 
 # The End
-This concludes Lab2, feel free to play around more with this dashboard if you want or you can proceed to [Lab3](lab3.md)
+This concludes Lab2, feel free to play around more with this dashboard if you want or you can proceed to [DMZ Deployment](dmz-deploy.md) instructions