Merge branch 'main' into feature/1968-topology-applications

# Conflicts:
#	keep-ui/utils/hooks/useTopology.ts

.pre-commit-config.yaml

@@ -7,12 +7,6 @@ repos:
         language: system
         types: [python]
         require_serial: true
-    #  - id: yamllint
-    #    name: yamllint
-    #    description: This hook runs yamllint.
-    #    entry: yamllint
-    #    language: python
-    #    types: [file, yaml]
       - id: end-of-file-fixer
         name: Fix End of Files
         entry: end-of-file-fixer
@@ -38,10 +32,17 @@ repos:
     hooks:
       # Run the linter.
       - id: ruff
-        args: [ --fix ]
+        args: [--fix]
   - repo: https://github.com/compilerla/conventional-pre-commit
     rev: v2.1.1
     hooks:
       - id: conventional-pre-commit
         stages: [commit-msg]
         args: [] # optional: list of Conventional Commits types to allow e.g. [feat, fix, ci, chore, test]
+  - repo: https://github.com/pre-commit/mirrors-prettier
+    rev: v3.0.3
+    hooks:
+      - id: prettier
+        types_or:
+          [javascript, jsx, ts, tsx, json, yaml, css, scss, html, markdown]
+        args: [--write]

docs/deployment/stress-testing.mdx

@@ -46,7 +46,7 @@ The primary parameters that affect the specification requirements for Keep are:
 3. **High Volume (100,000 - 1,000,000 total alerts, 5000's of alerts per day)**:
    - **Setup**: Deploy Keep with Elasticsearch for storing alerts as documents.
    - **Expectations**: The system should maintain performance levels despite the large alert volume, with increased resource usage managed through scaling strategies.
-4. **Very High Volume (> 1,000,000 total alerts, 10k's of alerts per day)
+4. **Very High Volume (> 1,000,000 total alerts, 10k's of alerts per day)**:
     - **Setup**: Deploy Keep with Elasticsearch for storing alerts as documents.
     - **Setup #2**: Deploy Keep with Redis and with ARQ to use Redis as a queue.