Merge branch 'main' into clean-detections-and-alert-page

Author: nastasha-solomon

raw-migrated-files/docs-content/serverless/security-automatic-import.md

@@ -103,8 +103,6 @@ toc:
       - file: docs-content/serverless/project-setting-data.md
       - file: docs-content/serverless/project-settings-alerts.md
       - file: docs-content/serverless/project-settings-content.md
-      - file: docs-content/serverless/security-automatic-import.md
-      - file: docs-content/serverless/security-vuln-management-faq.md
       - file: docs-content/serverless/what-is-observability-serverless.md
   - file: elasticsearch-hadoop/elasticsearch-hadoop/index.md
     children:
@@ -145,7 +143,6 @@ toc:
     children:
       - file: observability-docs/observability/index.md
       - file: observability-docs/observability/obs-ai-assistant.md
-  - file: security-docs/security/index.md
   - file: stack-docs/elastic-stack/index.md
     children:
       - file: stack-docs/elastic-stack/installing-stack-demo-self.md

raw-migrated-files/docs-content/serverless/security-vuln-management-faq.md

@@ -198,7 +198,7 @@ Enable tail-based sampling with [Enable tail-based sampling](../../../solutions/
 Trace events are matched to policies in the order specified. Each policy list must conclude with a default policy — one that only specifies a sample rate. This default policy is used to catch remaining trace events that don’t match a stricter policy. Requiring this default policy ensures that traces are only dropped intentionally. If you enable tail-based sampling and send a transaction that does not match any of the policies, APM Server will reject the transaction with the error `no matching policy`.
 
 ::::{important}
-Please note that from version `8.3.1` APM Server implements a default storage limit of 3GB, but, due to how the limit is calculated and enforced the actual disk space may still grow slightly over the limit.
+Please note that from version `9.0.0` APM Server has an unlimited storage limit, but will stop writing when the disk where the database resides reaches 80% usage. Due to how the limit is calculated and enforced, the actual disk space may still grow slightly over this disk usage based limit, or any configured storage limit.
 ::::