Merge pull request #57 from NextronSystems/v4

chore: data retention settings

Author: redteampanda-ng

images/cockpit_data-retention-settings.png

@@ -45,7 +45,7 @@ There are multiple options within the Data Retention Policy:
 - **Event Retention per Case** - this setting will allow you to set a
   different retention period rule for each case. This is useful if you have
   different retention requirements for different cases. This value takes
-  presedence over the **Event Retention per Case Type / Status**. You can
+  precedence over the **Event Retention per Case Type / Status**. You can
   choose from the following options:
 
   - **Default** - uses retention period from the General Event Retention setting.
@@ -63,7 +63,7 @@ There are multiple options within the Data Retention Policy:
   Raw data on disk will not be deleted. The default setting is to keep all
   events indefinitely. We recommend to only use this setting if necessary,
   as it will delete all events older than the specified number of days.
-  The reason for this is that this setting is taking presedence over the
+  The reason for this is that this setting is taking precedence over the
   other settings. Please use this option with caution.
 
   .. figure:: ../images/cockpit_data-retention-general.png
@@ -78,3 +78,20 @@ There are multiple options within the Data Retention Policy:
       :alt: Data Retention - Others
 
       Data Retention - Others
+
+- **Settings** – These settings specify when events should be deleted.
+  Change the ``Daily Schedule`` to avoid slowing down your system during
+  working hours of your analysts.
+  The ``Expunge Deleted Events`` value is used for the above **Data
+  Retention Policies**, as the actions taken here only soft-delete events,
+  meaning the affected events are not deleted immediately, but rather
+  marked for deletion. All your events are stored inside specific indices,
+  and rewriting those takes (CPU) time. This is why we reindex indices
+  only when an index contains a specific percentage of deleted events
+  (by default, 20%). If you need more free disk space, lower this threshold.
+  If you're experiencing high CPU load, you can raise it.
+
+  .. figure:: ../images/cockpit_data-retention-settings.png
+      :alt: Data Retention - Settings
+
+      Data Retention - Settings

images/cockpit_data-retention.png

@@ -1,24 +1,5 @@
 .. Index:: Pitfalls
 
-Certificate Validation Failed
------------------------------
-
-If you receive the following error, SSL/TLS interception interrupted the
-installation process.
-
-.. code-block:: console
-   
-   nextron@cockpit:~$ sudo nextronInstaller -cockpit 
-   [sudo] password for nextron:
-   Ign:1 https://update3.nextron-systems.com analysis InRelease
-   Err:2 https://update3.nextron-systems.com analysis Release
-   Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 192.168.3.21 8080]
-
-Since we do not support setups in which the connections to our update
-servers are intercepted (see chapter :ref:`requirements/network:ssl/tls interception`), the
-only way to resolve this problem is to deactivate SSL/TLS interception
-for our update servers.
-
 Log File Import of Previous Years
 ---------------------------------
 
@@ -153,7 +134,7 @@ Broken before Analysis Cockpit Installation
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 If you have set a wrong proxy while the Debian setup and the connectivity test fails, 
-edit the proxy settings in the Web GUI of the NEXTRON Universal Installer:
+edit the proxy settings in the Web GUI of the Nextron Universal Installer:
 
 ``Settings`` > ``Proxy``