Merge branch 'main' into Cisco-AMP-App

Author: himanshu219

blog-service/2023/12-31.md

@@ -758,7 +758,9 @@ We're excited to announce the release of our new cloud-to-cloud source for Trell
 
 We’re happy to announce a new security option allowing administrators to set a custom policy for the number of days an API Access Key can go unused before being automatically deactivated. This setting allows administrators to tailor the feature to suit their organization’s specific security requirements. This enhances the security of your account by reducing the risk of unauthorized access through abandoned access keys. This ensures that only active access keys can be used to access your account and its resources.
 
-To access this feature, log in to your account and navigate to **Administration > Security > Policies**. From there, you can set your preferred policy for deactivation of unused access keys. [Learn more](/docs/manage/security/access-keys#edit-deactivate-or-delete-an-access-key).
+To access this feature, log in to your account and navigate to **Policies**.  [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Security > Policies**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Administration**, and then under **Account Security Settings** select **Policies**. You can also click the **Go To...** menu at the top of the screen and select **Policies**. 
+
+From there, you can set your preferred policy for deactivation of unused access keys. [Learn more](/docs/manage/security/access-keys#edit-deactivate-or-delete-an-access-key).
 
 
 ---

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

@@ -17,7 +17,7 @@ We're excited to announce that when you create a role, you can select **Index Ac
 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 December 16, 2024.
+These changes are rolling out across deployments incrementally and will be available on all deployments by January 10, 2025.
 :::
 
 [Learn more](/docs/manage/users-roles/roles/create-manage-roles/#create-a-role).

docs/contributing/style-guide.md

@@ -1533,6 +1533,8 @@ If you need to use mouse actions to be specific, use:
 
 ## Videos
 
+### YouTube
+
 To embed a YouTube video on a doc:
 
 1. Copy and paste the following code into your page (including the `import Iframe` line).
@@ -1596,3 +1598,50 @@ import Iframe from 'react-iframe';
 
 </TabItem>
 </Tabs>
+
+### Other video types
+
+You can use similar coding to embed videos from other vendors than YouTube. Following is example coding to embed videos from Wistia. 
+
+<Tabs
+  className="unique-tabs"
+  defaultValue="Markdown"
+  values={[
+    {label: 'Markdown', value: 'Markdown'},
+    {label: 'Result', value: 'Result'},
+  ]}>
+
+<TabItem value="Markdown">
+
+```html
+<Iframe url="https://fast.wistia.net/embed/iframe/yebz0v90tx?web_component=true&seo=true&videoFoam=false"
+  width="854px"
+  height="480px"
+  id="wistiaVideo"
+  className="video-container"
+  display="initial"
+  position="relative"
+  allow="autoplay; fullscreen"
+  allowfullscreen
+/>
+```
+
+</TabItem>
+<TabItem value="Result">
+
+<Iframe url="https://fast.wistia.net/embed/iframe/yebz0v90tx?web_component=true&seo=true&videoFoam=false"
+  width="854px"
+  height="480px"
+  id="wistiaVideo"
+  className="video-container"
+  display="initial"
+  position="relative"
+  allow="autoplay; fullscreen"
+  allowfullscreen
+/>
+</TabItem>
+</Tabs>
+
+:::note
+Typically you must include `import Iframe from 'react-iframe';` with the markdown. It is not included in the example above because it was already called in the previous markdown for YouTube.
+:::

docs/cse/administration/mitre-coverage.md

@@ -24,6 +24,7 @@ Coverage data is updated on the page once a day. To determine your coverage, the
 
 Watch this micro lesson to learn about the MITRE ATT&CK Threat Coverage Explorer.
 
+<!-- old YouTube video embedding
 <Iframe url="https://www.youtube.com/embed/O1SmpbL4gos?rel=0"
      width="854px"
      height="480px"
@@ -34,6 +35,18 @@ Watch this micro lesson to learn about the MITRE ATT&CK Threat Coverage Explorer
      allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
      allowfullscreen
      />
+-->
+
+<Iframe url="https://fast.wistia.net/embed/iframe/yebz0v90tx?web_component=true&seo=true&videoFoam=false"
+  width="854px"
+  height="480px"
+  id="wistiaVideo"
+  className="video-container"
+  display="initial"
+  position="relative"
+  allow="autoplay; fullscreen"
+  allowfullscreen
+/>
 
 ## User interface 
 

docs/integrations/microsoft-azure/azure-api-management.md

@@ -26,9 +26,9 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat
 * Logs collection from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) using our [Azure Event Hubs source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
 * Metrics collection using our [HTTP Logs and Metrics source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/) via Azure Functions deployed using the ARM template.
 
-You must explicitly enable diagnostic settings for each Azure API Management service you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
+You must explicitly enable diagnostic settings for each Azure API Management service you want to monitor. You can forward logs to the same Event Hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
 
-When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/APIManagement/Logs`, `Azure/APIManagement/Metrics`.
+When you configure the Event Hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/APIManagement/Logs`, `Azure/APIManagement/Metrics`.
 
 ### Configure field in field schema
 
@@ -112,14 +112,14 @@ If this rule already exists, there is no need to create it again.
    | service_type     | $resourceId._6 |
    | service_name     | $resourceId._7 |
 
-#### Azure observability metadata extraction application gateway level
+#### Azure observability metadata extraction Azure API management level
 
    ```sql
-   Rule Name: AzureObservabilityMetadataExtractionAppGatewayLevel
+   Rule Name: AzureObservabilityMetadataExtractionAzureAPIManagementLevel
    ```
    
    ```sql title="Metric match expression"
-   resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/*/APPLICATIONGATEWAYS/* tenant_name=*
+   resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/MICROSOFT.APIMANAGEMENT/SERVICE/* tenant_name=*
    ```
    | Fields extracted  | Metric rule             |
    |:------------------|:------------------------|
@@ -139,7 +139,7 @@ In this section, you will configure a pipeline for shipping metrics from Azure M
 1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Azure API Management that you want to monitor.
    1. Choose `Stream to an event hub` as destination.
    1. Select `AllMetrics`.
-   1. Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name. <br/><img src={useBaseUrl('img/send-data/azure-apimanagement-metrics.png')} alt="Azure application gateway metrics" style={{border: '1px solid gray'}} width="800" />
+   1. Use the Event Hub namespace created by the ARM template in Step 2 above. You can create a new Event Hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name. <br/><img src={useBaseUrl('img/send-data/azure-apimanagement-metrics.png')} alt="Azure API management metrics" style={{border: '1px solid gray'}} width="800" />
 1. Tag the location field in the source with right location value. <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure API Management Tag Location" style={{border: '1px solid gray'}} width="400" />
    
 :::note
@@ -153,7 +153,7 @@ In the v2 service tiers, API Management has replaced the capacity metric with se
 In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
 
 1. To set up the Azure Event Hubs source in Sumo Logic, refer to the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
-1. To create the diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the steps below for each Azure application gateway account that you want to monitor.
+1. To create the diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the steps below for each Azure API management account that you want to monitor.
    1. Choose **Stream to an event hub** as the destination.
    1. Select `allLogs`.
    1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/send-data/azure-apimanagement-logs.png')} alt="Azure API Management logs" style={{border: '1px solid gray'}} width="800" />