docs: Updated charter/packages/twistlock/Architecture.md to describe how to enable logging

charter/packages/twistlock/Architecture.md

@@ -11,10 +11,10 @@ graph LR
   subgraph "Twistlock"
     twistlockpods("Twistlock Pod(s)")
     twistlockservice{{Twistlock Console}} --> twistlockpods("TwistlockPod(s)")
-  end   
+  end
   subgraph "Ingress"
     ig(Ingress Gateway) --"App Port"--> twistlockservice
-  end  
+  end
   subgraph "Logging"
     twistlockpods("Twistlock Pod(s)") --"Logs"--> fluent(Fluentbit) --> logging-ek-es-http
     logging-ek-es-http{{Elastic Service<br />logging-ek-es-http}} --> elastic[(Elastic Storage)]
@@ -31,6 +31,10 @@ graph LR
 Twistlock Console serves as the user interface within Twistlock. The graphical
 user interface (GUI) lets you define policy, configure and control your Twistlock deployment, and view the overall health (from a security perspective) of your container environment
 
+### Logging
+In order to enable logging this can only be done via the console UI. Logging can be enabled by clicking on the `Manage` dropdown and click `Alerts`. Under the `Logging` tab the option for `Stdout` can be set to Enabled. This allows for options for logging to stdout to be scraped by fluentbit/promtail OR log to the underlying hosts.
+
+
 ### Install Defender
 
 In Bigbang the  twistlock defender is installed manual.