Merge branch 'main' into fields-icons

Author: kimsauce

docs/manage/security/scim/provision-with-microsoft-entra-id.md

@@ -73,20 +73,23 @@ Create roles that the users will have in Sumo Logic (for example, `Analyst` and
    1. Click **Test Connection**. If successful, a message like this appears: **Testing connection to `<app name>`. The supplied credentials are authorized to enable provisioning**.
 1. Set up mappings:
    1. Select **Mappings** and **Provision Microsoft Entra Users**.<br/><img src={useBaseUrl('img/security/provision-azure-mappings.png')} alt="Provision mappings" style={{border: '1px solid gray'}} width="600" />
+   1. Go to **Attribute Mapping**, select **Show advanced options**, and select **Edit attribute list for customappsso**.
+       1. For the **roles** attribute select **string** for the **Type**, and select the **Multi-Value?** checkbox to allow users to have multiple roles.<br/><img src={useBaseUrl('img/security/roles-advanced-options.png')} alt="Advanced options for the roles attribute" style={{border: '1px solid gray'}} width="600" />
+       1. Click **Save**.
    1. At the bottom of the **Attribute Mapping** dialog, select **Add New Mapping**.
    1. Fill out the **Edit Attribute** dialog:
       1. For **Mapping type** select **Expression**.
-      1. For **Expression** enter `AppRoleAssignments([appRoleAssignments])`.
-      1. For **Target attribute** select `roles[primary eq "True"].value`.
+      1. For **Expression** enter `AppRoleAssignmentsComplex([appRoleAssignments])`.
+      1. For **Target attribute** select `roles`.
       1. Click **OK**.<br/><img src={useBaseUrl('img/security/provision-azure-role-attribute.png')} alt="Edit attribute" style={{border: '1px solid gray'}} width="600" />
    1. On the **Attribute Mapping** dialog, delete all the attributes except:
       * userName
       * active
       * emails[type eq "work"].value
       * name.givenName
       * name.familyName
-      * roles[primary eq "True"].value
-   1. Click **Save**.<br/><img src={useBaseUrl('img/security/provision-azure-attribute-mappings.png')} alt="Attribute mappings" style={{border: '1px solid gray'}} width="600" />
+      * roles<br/><img src={useBaseUrl('img/security/provision-azure-attribute-mappings.png')} alt="Attribute mappings" style={{border: '1px solid gray'}} width="600" />
+   1. Click **Save**.
 1. Click the **Home > `<app name>` | Provisioning** link in the top left corner of the screen. This returns you to the **Provisioning** tab.
 1. Test provisioning:
    1. In the app, select **Manage > Provisioning**.

docs/metrics/manage-metric-volume/data-limits-for-metrics.md

@@ -5,6 +5,8 @@ sidebar_label: Data Limits for Metrics
 description: It is important to understand the volume of metrics that you are ingesting into Sumo Logic.
 ---
 
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
 This page describes the limits Sumo Logic enforces on the metrics you ingest into Sumo Logic, including data volume limits and metadata-related limits.
 
 :::note
@@ -102,13 +104,13 @@ The value of a metadata item, whether it is a dimension, metatag, or metadata re
 
 #### Audit logging 
 
-When one of the limits described above is exceeded, Sumo Logic creates a `MetricsMetadataLimitsExceeded` Health Event for the associated Metric Source and writes an error or warning message to the Audit Event Index.
+When one of the limits described above is exceeded, Sumo Logic creates a [`MetricsMetadataLimitsExceeded`](https://service.sumologic.com/audit/docs/#operation/getMetricsMetadataLimitsExceeded) Health Event for the associated Metric Source and writes an error or warning message to the [System Event Index](/docs/manage/security/audit-indexes/system-event-index/).
 
-Here is an example of a Health Event for a Metrics Source that sent offending metrics:
+Here is an example of a [Health Event](/docs/manage/health-events) for a Metrics Source that sent offending metrics:
 
-![metadata-health-event.png](/img/metrics/metadata-health-event.png)
+<img src={useBaseUrl('/img/metrics/metadata-health-event.png')} alt="MetricsMetadataLimitsExceeded health event error" style={{border: '1px solid gray'}} width="400" />
 
-Here is an example of an Audit Event Index message generated when
+Here is an example of a System Event Index message generated when
 metrics sent to Sumo Logic exceed the metadata value limit.
 
 ```json

docs/send-data/collection/restart-collectors.md

@@ -1,21 +1,11 @@
 ---
 id: restart-collectors
-title: Restart a Collector (Beta)
+title: Restart a Collector
 description: Learn how to restart a Collector from the Collection page.
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-<head>
-  <meta name="robots" content="noindex" />
-</head>
-
-<p><a href="/docs/beta"><span className="beta">Beta</span></a></p>
-
-<!-- Originally added as a beta article with SUMO-175343. -->
-
-This feature is in Beta. To participate, contact your Sumo Logic account executive.
-
 This document explains how to initiate a request to restart an Installed
 Collector from the Collection page. The other option is to [start or stop a Collector using our provided scripts](start-stop-collector-using-scripts.md).
 

sidebars.ts

@@ -776,6 +776,7 @@ module.exports = {
           items: [
             'send-data/collection/search-for-a-collector-or-source',
             'send-data/collection/start-stop-collector-using-scripts',
+            'send-data/collection/restart-collectors',
             'send-data/collection/edit-collector',
             'send-data/collection/edit-source',
             'send-data/collection/pause-resume-source',