Merge branch 'master' into firehose-version

.github/workflows/pr_validate.yaml

@@ -11,6 +11,9 @@ jobs:
     runs-on: ubuntu-latest
     env:
       MANIFEST_PATH: '_manifest/validation_manifest.json'
+    permissions:
+      contents: 'write'
+      packages: 'read'
     steps:
       - name: Checkout PR
         uses: actions/checkout@v4
@@ -103,7 +106,7 @@ jobs:
           file_pattern: './static/manifest.json'
           commit_message: 'auto generated manifest'
           commit_options: "--no-gpg-sign"
-          push_options: '--force'
+          push_options: '--force'      
       - name: Manifest update success
         if: steps.create_manifest.outputs.skip_next_step != 'true' && steps.run_validation.outputs.skip_next_step != 'true'
         run: |

docs/user-guide/data-hub/log-parsing/sawmill-parsing.md

@@ -6,7 +6,9 @@ description: Learn how to parse your logs in Logz.io
 keywords: [log, monitoring, parsing, default parsing, built in log types, log types, observability]
 ---
 
-
+:::warning Note
+The Data Parsing editor will be **shut down** on August 30th, 2024. For the foreseeable future, you can contact [[email protected]](mailto:[email protected]) to assist with parsing your data.
+:::
 
 
 Parsing is the process of breaking down your log message into smaller chunks of data,

docs/user-guide/quick-start.md

@@ -53,8 +53,6 @@ Logz.io offers automatic parsing [for over 50 log types](https://docs.logz.io/do
 
 If you can't find your log type, or if you're interested in sending custom logs, Logz.io will parse the logs for you. Parsing-as-a-service is included in your Logz.io subscription; just open a chat with our **Support team** with your request, you can also email us at [[email protected]](mailto:[email protected]).
 
-If you prefer to parse the logs yourself, you can use our [DIY Data Parsing Editor](https://docs.logz.io/docs/user-guide/data-hub/log-parsing/sawmill-parsing/).
-
 ###### Additional resources