Merge branch 'main' into DOCS-467

Author: kimsauce

.clabot

@@ -170,7 +170,9 @@
     "ishaanahuja29",
     "raunakmandaokar",
     "bradtho",
-    "Misterjohnson87"
+    "Misterjohnson87",
+    "lol3909",
+    "Hellfire4959"
   ],
   "message": "Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please [sign your name here](https://forms.gle/YgLddrckeJaCdZYA6) and we'll add you to our approved list of contributors.",
   "label": "cla-signed",

blog-service/2023/12-31.md

@@ -106,7 +106,7 @@ To learn more, see [Updating Your AWS Observability Stack](/docs/observability/a
 
 We're excited to announce that you can use roles to restrict access to specific data in search indexes. When you create a role, you can select **Index based** filters to allow access to data based on indexes, or you can select **Advanced filter** to define a dataset to allow access based on search criteria. This ensures that users only see the data they are supposed to.
 
-[Learn more](/docs/manage/users-roles/roles/rbac-for-indexes).
+[Learn more](/docs/manage/users-roles/roles/create-manage-roles/).
 
 :::note
 This feature is in Beta. To participate, contact your Sumo Logic account executive or our Support Team.

blog-service/2024-10-14-collection.md

@@ -0,0 +1,14 @@
+---
+title: Automox C2C Source (Collection)
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+  - collection
+  - automox
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
+
+We're excited to announce the release of our new cloud-to-cloud source for Automox. This source helps you to collect all events objects, audit trail events, and device inventory details from the Automox platform, and ingest them into Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/automox-source).

blog-service/2024-10-14-manage.md

@@ -0,0 +1,23 @@
+---
+title: Role Based Index Access (Manage)
+image: https://www.sumologic.com/img/logo.svg
+keywords:
+  - rbac
+  - index
+  - roles
+hide_table_of_contents: true
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
+
+We're excited to announce that when you create a role, you can select **Index Access** to restrict access to data in specific indexes. In addition, when you now select **Search Filter**, you can create filtering to restrict access to log analytics, audit, and security data. These enhancements ensure that users only see the data they are supposed to. 
+
+This feature was [previously only available to participants in our beta program](/release-notes-service/2023/12/31/#october-27-2023-manage-account). It is now available for general use.
+
+:::note
+These changes are rolling out across deployments incrementally and will be available on all deployments by October 25, 2024.
+:::
+
+[Learn more](/docs/manage/users-roles/roles/create-manage-roles/#create-a-role).

blog-service/2024-10-15-collection.md

@@ -0,0 +1,14 @@
+---
+title: Kandji C2C Source (Collection)
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+  - collection
+  - kandji
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
+
+We're excited to announce the release of our new cloud-to-cloud source for Kandji. This source helps you to collect threat details, device lists, activity logs, and device information from the Kandji platform, and ingest them into Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/kandji-source).

cid-redirects.json

@@ -2616,6 +2616,8 @@
   "/cid/19878": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/airtable-source",
   "/cid/19879": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/knowbe4-api-source",
   "/cid/16323": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/druva-source",
+  "/cid/13428": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/kandji-source",
+  "/cid/17343": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/automox-source",
   "/cid/20172": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/cisco-vulnerability-management-source",
   "/cid/19880": "/docs/metrics/metrics-operators/predict",
   "/cid/19881": "/docs/metrics/metrics-operators/accum",
@@ -2725,7 +2727,7 @@
   "/cid/21037": "/docs/integrations/google/cloud-vpn",
   "/cid/21038": "/docs/integrations/containers-orchestration/vmware-tanzu-application-service",
   "/cid/10999": "/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source",
-  "/cid/11000": "/docs/alerts/monitors/automation-payload-variables",
+  "/cid/11000": "/docs/platform-services/automation-service/automation-service-playbooks",
   "/Cloud_SIEM_Enterprise": "/docs/cse",
   "/Cloud_SIEM_Enterprise/Administration": "/docs/cse/administration",
   "/Cloud_SIEM_Enterprise/Administration/Cloud_SIEM_Enterprise_Feature_Update_(2022)": "/docs/cse/administration",
@@ -3410,6 +3412,7 @@
   "/Visualizations-and-Alerts/Alerts/02-Schedule-a-Search": "/docs/alerts/scheduled-searches",
   "/Visualizations-and-Alerts/Alerts/Alert_Grouping": "/docs/alerts/monitors/alert-grouping",
   "/Visualizations-and-Alerts/Alerts/Alert_Variables": "/docs/alerts/monitors/alert-variables",
+  "/docs/alerts/monitors/automation-payload-variables": "/docs/platform-services/automation-service/automation-service-playbooks",
   "/Visualizations-and-Alerts/Alerts/Monitors": "/docs/alerts/monitors",
   "/Visualizations-and-Alerts/Alerts/Monitors/About_Monitors": "/docs/alerts/monitors/overview",
   "/Visualizations-and-Alerts/Alerts/Monitors/Monitor_FAQ": "/docs/alerts/monitors/monitor-faq",
@@ -3638,7 +3641,7 @@
   "/Beta/Cloud-to-Cloud_Integration_Framework/Workday_Source": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/workday-source",
   "/Beta/Dashboard-Data-API": "/docs/api/dashboard",
   "/Beta/Dashboard_(New)": "/docs/dashboards",
-  "/Beta/Grant_Access_to_Data_in_Audit_Indexes": "/docs/manage/security/audit-indexes/audit-index-access",
+  "/Beta/Grant_Access_to_Data_in_Audit_Indexes": "/docs/manage/users-roles/roles/create-manage-roles",
   "/Beta/Health_Events": "/docs/manage/health-events",
   "/Beta/Ingest_Budgets": "/docs/manage/ingestion-volume/ingest-budgets",
   "/docs/manage/ingestion-volume/ingest-budgets/assign-collector-ingest-budget": "/docs/manage/ingestion-volume/ingest-budgets/daily-volume/assign-collector-ingest-budget",
@@ -3993,7 +3996,9 @@
   "/docs/manage/security/audit-index": "/docs/manage/security/audit-indexes/audit-index",
   "/docs/manage/security/audit-event-index": "/docs/manage/security/audit-indexes/audit-event-index",
   "/docs/manage/security/search-audit-index": "/docs/manage/security/audit-indexes/search-audit-index",
-  "/docs/manage/security/audit-index-access": "/docs/manage/security/audit-indexes/audit-index-access",
+  "/docs/manage/security/audit-index-access": "/docs/manage/users-roles/roles/create-manage-roles",
+  "/docs/manage/security/audit-indexes/audit-index-access/": "/docs/manage/users-roles/roles/create-manage-roles",
+  "/docs/manage/users-roles/roles/rbac-for-indexes": "/docs/manage/users-roles/roles/create-manage-roles",
   "/cid/-1": "/",
   "/docs/api/beta": "/docs/api",
   "/docs/api/dashboard-data": "/docs/api/dashboard",

docs/alerts/monitors/automation-payload-variables.md

@@ -78,10 +78,4 @@ In this section, we'll introduce the following concepts:
   <p>Learn how to use Automation Service playbooks with monitors.</p>
   </div>
 </div>
-<div className="box smallbox card">
-  <div className="container">
-  <a href="/docs/alerts/monitors/automation-payload-variables"><img src={useBaseUrl('img/icons/operations/monitor-and-visualize.png')} alt="icon" width="40"/><h4>Automation Payload Variables</h4></a>
-  <p>Learn details about variables passed from a monitor to a playbook in the Automation Service.</p>
-  </div>
-</div>
 </div>

docs/alerts/monitors/index.md

@@ -155,7 +155,7 @@ Some integrations that have useful actions for monitors include:
 
 ### Pass custom fields from a monitor to playbooks
 
-Results from an alert query are passed to a playbook through the [automation payload](/docs/alerts/monitors/automation-payload-variables/). The variables from the payload can be used as inputs for different nodes in the playbook after they are defined as parameters in the start node.
+Results from an alert query are passed to a playbook through the [alert payload](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload). The variables from the payload can be used as inputs for different nodes in the playbook after they are defined as parameters in the start node.
 
 :::note
 You must use [alert grouping](/docs/alerts/monitors/alert-grouping/) in the monitor configuration to pass fields from the query to the playbook.
@@ -165,12 +165,12 @@ You must use [alert grouping](/docs/alerts/monitors/alert-grouping/) in the moni
 
 1. Click **Edit** on the Start Node.
 1. Select **Alert** from the dropdown. <br/><img src={useBaseUrl('img/alerts/parse_from_alert.png')} alt="Payload parameters from an alert" style={{border: '1px solid gray'}} width="700" />
-1. The parameters from the default [automation payload variables](/docs/alerts/monitors/automation-payload-variables/) will be defined, along with some placeholders for custom fields that may be passed from the alert query. To reference a field passed from the alert query, use `customPlaceholderMap[].FIELDNAME`.
+1. The parameters from the default [alert payload variables](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload) will be defined, along with some placeholders for custom fields that may be passed from the alert query. To reference a field passed from the alert query, use `customPlaceholderMap[].FIELDNAME`.
 
-#### Configure Parameters from a JSON Payload
+#### Configure parameters from a JSON payload
 
 1. Click **Edit** on the Start Node.
 1. Select **Parse from Json** from the dropdown. <br/><img src={useBaseUrl('img/alerts/parse_from_json.png')} alt="Payload parameters from a Json payload" style={{border: '1px solid gray'}} width="700" />
-1. Copy the payload from a previously triggered automation. You can view the playbook payload of a previously triggered alert by following the steps [here](/docs/alerts/monitors/automation-payload-variables/#view-playbook-payload).
+1. Copy the payload from a previously triggered automation. You can view the playbook payload of a previously triggered alert by following the steps [here](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload).
 1. Paste the payload into the **Enter Json payload** text box and click **Parse**. The fields from the payload will be auto parsed to parameters. <br/><img src={useBaseUrl('img/alerts/parse_from_json_payload.png')} alt="Parse from Json payload" style={{border: '1px solid gray'}} width="700" />
 1. Add or remove parameters based on the playbook requirements and click **Update**. <br/><img src={useBaseUrl('img/alerts/parse_from_json_parameters.png')} alt="Json Payload parameters" style={{border: '1px solid gray'}} width="700" />