Update Azure Storage with Azure metrics source compatibility

docs/integrations/microsoft-azure/azure-storage.md

@@ -59,121 +59,15 @@ 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/).
 * Activity 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/). It is recommended to create a separate source for activity logs. If you are already collecting these logs, you can skip this step.
-* 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.
+* Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
 
 You must explicitly enable diagnostic settings for each storage service (blob, queue, table, and file) and each storage account that 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/Storage/Logs`, `Azure/Storage/Metrics`.
 
-### Configure field in field schema
-1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**. 
-1. Search for following fields:
-   - `tenant_name`. This field is tagged at the collector level and users can get the tenant name using the instructions here https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name
-   - `location`. The region to which the resource name belongs.
-   - `subscription_id`. Id associated with a subscription where the resource is present.
-   - `resource_group`. The resource group name where the Azure resource is present.
-   - `provider_name`. Azure resource provider name (for example, Microsoft.Storage).
-   - `resource_type`. Azure resource type (for example, storageaccounts).
-   - `resource_name`. The name of the resource (for example, storage account name).
-   - `service_type`. Type of the service that can be accessed from with an Azure resource (for example, blobservices).
-   - `service_name`. Services that can be accessed from within an Azure resource (for example, Azure SQL databases in Azure SQL Server).
-
-
-3. Create the fields if it is not present. Refer to [create and manage fields](/docs/manage/fields/#manage-fields).
-
-### Configure Field Extraction Rules
-
-Create a Field Extraction Rule (FER) for Azure Storage by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/).
-
-* **Azure Location Extraction FER**
-
-   ```sql
-   Rule Name: AzureLocationExtractionFER
-   Applied at: Ingest Time
-   Scope (Specific Data): tenant_name=*
-   ```
-
-   ```sql title="Parse Expression"
-   json "location", "properties.resourceLocation", "properties.region" as location, resourceLocation, service_region nodrop
-   | replace(toLowerCase(resourceLocation), " ", "") as resourceLocation
-   | if (!isBlank(resourceLocation), resourceLocation, location) as location
-   | if (!isBlank(service_region), service_region, location) as location 
-   | if (isBlank(location), "global", location) as location
-   | fields location
-   ```
-
-* **Resource ID Extraction FER**
-
-   ```sql
-   Rule Name: AzureResourceIdExtractionFER
-   Applied at: Ingest Time
-   Scope (Specific Data): tenant_name=*
-   ```
-
-   ```sql title="Parse Expression"
-   json "resourceId", "ResourceId" as resourceId1, resourceId2 nodrop
-    | if (isBlank(resourceId1), resourceId2, resourceId1) as resourceId
-    | toUpperCase(resourceId) as resourceId
-    | parse regex field=resourceId "/SUBSCRIPTIONS/(?<subscription_id>[^/]+)" nodrop
-    | parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop
-    | parse regex field=resourceId "/PROVIDERS/(?<provider_name>[^/]+)" nodrop
-    | parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?<resource_type>[^/]+)/(?<resource_name>.+)" nodrop
-    | parse regex field=resource_name "(?<parent_resource_name>[^/]+)(?:/PROVIDERS/[^/]+)?/(?<service_type>[^/]+)/?(?<service_name>.+)" nodrop
-    | if (isBlank(parent_resource_name), resource_name, parent_resource_name) as resource_name
-    | fields subscription_id, location, provider_name, resource_group, resource_type, resource_name, service_type, service_name
-   ```
-### Configure metric rules
-
-  * **Azure Observability Metadata Extraction Service Level**
-
-      In case this rule is already exists then no need to create again.
-```sql
-Rule Name: AzureObservabilityMetadataExtractionServiceLevel    
-```
-
-```sql title="Metric match expression"
-resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/*/*/*/*/* tenant_name=*
-```
-| Fields extracted | Metric rule    |
-|------------------|----------------|
-| subscription_id  | $resourceId._1 |
-| resource_group   | $resourceId._2 |
-| provider_name    | $resourceId._3 |
-| resource_type    | $resourceId._4 |
-| resource_name    | $resourceId._5 |
-| service_type     | $resourceId._6 |
-| service_name     | $resourceId._7 |
-
-* **Azure Observability Metadata Extraction Storage Account Level**
-```sql
-Rule Name: AzureObservabilityMetadataExtractionStorageAccountLevel
-```
-
-```sql title="Metric match expression"
-resourceId=*/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/*/*/* tenant_name=* accountresourceid=*
-```
-| Fields extracted | Metric rule    |
-|------------------|----------------|
-| subscription_id  | $resourceId._1 |
-| resource_group   | $resourceId._2 |
-| provider_name    | $resourceId._3 |
-| resource_type    | $resourceId._4 |
-| resource_name    | $resourceId._5 |
-
 ### Configure metrics collection
 
-In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
-
-1. Create a hosted collector and tag the `tenant_name` field
-   <img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Storage Tag Tenant Name" style={{border: '1px solid gray'}} width="800" />
-2. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
-1. [Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
-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 the steps below for each storage service (blob, queue, table, and file) and each storage account that you want to monitor.
-   * Choose `Stream to an event hub` as the destination.
-   * Select `Transaction`.
-   * 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 the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
-4. Tag the location field in the source with the right location value.
-   <img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Storage Tag Location" style={{border: '1px solid gray'}} width="500" />
+To set up the Azure Metrics source in Sumo Logic, refer to [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
 
 ### Configure logs collection
 
@@ -209,15 +103,27 @@ In **Defender Plans** settings page turn on the **Azure Storage** status under *
 
 Now that you have set up data collection, install the Azure Storage Sumo Logic app to use the pre-configured [dashboards](#viewing-the-azure-storage-app-dashboards) that provide visibility into your environment for real-time analysis of overall usage.
 
-import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2.md';
+import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md';
+
+<AppInstallIndexV2/>
 
-<AppInstallNoDataSourceV2/>
+As part of the app installation process, the following fields will be created by default:
+
+- `tenant_name`. This field is tagged at the collector level. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name).
+- `location`. The region the resource name belongs to.
+- `subscription_id`. ID associated with a subscription where the resource is present.
+- `resource_group`. The resource group name where the Azure resource is present.
+- `provider_name`. Azure resource provider name (for example, Microsoft.Network).
+- `resource_type`. Azure resource type (for example, storage accounts).
+- `resource_name`. The name of the resource (for example, storage account name).
+- `service_type`. Type of the service that can be accessed with an Azure resource.
+- `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions).
 
 ## Viewing the Azure Storage app dashboards
 
-import ViewDashboards from '../../reuse/apps/view-dashboards.md';
+import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md';
 
-<ViewDashboards/>
+<ViewDashboardsIndex/>
 
 ### Overview
 
@@ -444,6 +350,18 @@ import AppUninstall from '../../reuse/apps/app-uninstall.md';
 
 <AppUninstall/>
 
+### Azure Storage alerts
+These alerts are metric based and will work for all Azure Storage.
+
+| Alert Name                                      | Alert Description and Conditions                                                                                                                             | Alert Condition       | Recover Condition   |
+|:------------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------|:--------------------|
+| `Azure Storage - Availability`                  | This alert is triggered when average Availability is less than 90%. Also, a warning type alert will be triggered when average Availability is less than 95%. | Percentage < = 90     | Percentage > 90     |
+| `Azure Storage - Success E2E Latency`           | This alert is triggered  when Success E2E Latency is greater than 1000 MilliSeconds.                                                                         | MilliSeconds > = 1000 | MilliSeconds < 1000 |
+| `Azure Storage - Success Server Latency`        | This alert is triggered when Success Server Latency greater than 1000.                                                                                       | MilliSeconds > = 1000 | MilliSeconds < 1000 |
+| `Azure Storage - Transactions`                  | This alert is triggered when Transactions count greater than 500.                                                                                            | Count > = 500         | Count < 500         |
+| `Azure Storage - Used Capacity(GB)`             | This alert is triggered when Used Capacity(GB) greater than 100.                                                                                             | Byted(GB) > = 100     | Byted(GB) < 100     |
+
+
 ## Troubleshooting
 
 ### HTTP Logs and Metrics Source used by Azure Functions