Converted Responses to JSON, improved severity detection, and built a known issues feed

README.md

@@ -65,4 +65,30 @@ The script will start a continuous monitoring loop. Every 5 minutes, it will:
 
 The script will print its status and any detected anomalies to the console.
 
+## 4. Features
+
+### Priority System
+
+The monitoring agent uses a priority system to classify anomalies. The LLM is instructed to return a severity level for each anomaly it detects. The possible severity levels are:
+
+-   **high**: Indicates a critical issue that requires immediate attention. An alert is sent to Discord and Google Home.
+-   **medium**: Indicates a non-critical issue that should be investigated. No alert is sent.
+-   **low**: Indicates a minor issue or a potential false positive. No alert is sent.
+-   **none**: Indicates that no anomaly was detected.
+
+### Known Issues Feed
+
+The agent uses a `known_issues.json` file to provide the LLM with a list of known issues and their resolutions. This helps the LLM to avoid flagging resolved or expected issues as anomalies.
+
+You can add new issues to the `known_issues.json` file by following the existing format. Each issue should have an "issue" and a "resolution" key. For example:
+
+```json
+[
+    {
+        "issue": "CPU temperature spikes to 80C under heavy load",
+        "resolution": "This is normal behavior for this CPU model and is not a cause for concern."
+    }
+]
+```
+
 **Note on Mock Data:** The current version of the script uses mock data for system logs and network metrics. To use this in a real-world scenario, you would need to replace the mock data with actual data from your systems.