diff --git a/5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef b/5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef
index 18a81157..40438c65 100644
--- a/5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef
+++ b/5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef
@@ -46,6 +46,30 @@
       },
       "revId": "5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": false,
+      "key": {
+        "uuid": "d602a5d4_b25623d2",
+        "filename": "fm-doc/fm_doc/events.yaml",
+        "patchSetId": 3
+      },
+      "lineNbr": 3665,
+      "author": {
+        "id": 9926
+      },
+      "writtenOn": "2024-04-25T13:44:08Z",
+      "side": 1,
+      "message": "A log would appear in \u0027fm event-list\u0027 though it wouldnt have a state of raised/cleared that an alarm would. \n\nGenerally alarms should be for fault conditions that may require admin/customer attention. Ideally, the service should be able to retrieve its service state without dependency on fm.",
+      "parentUuid": "bfdbddd1_5547eb12",
+      "range": {
+        "startLine": 3665,
+        "startChar": 10,
+        "endLine": 3665,
+        "endChar": 15
+      },
+      "revId": "5e0f635c6bbaaf8d7434f2ede51a93b9006b85ef",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     }
   ]
 }
\ No newline at end of file