Update azure-functions.md

amee-sumo · web-flow · commit 27cf31a5e8aa · 2025-04-02T22:35:57.000+05:30
diff --git a/docs/integrations/microsoft-azure/azure-functions.md b/docs/integrations/microsoft-azure/azure-functions.md
@@ -9,7 +9,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('img/integrations/microsoft-azure/azure-functions.png')} alt="thumbnail icon" width="45"/>
 
-[Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview) is a serverless solution that allows you to write less code, maintain less infrastructure, and save on costs. This integration helps in monitoring the health, tracking executions, and estimating cost of your function apps.
+[Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview) is a serverless solution that allows you to write less code, maintain less infrastructure, and save on costs. This integration helps in monitoring the health, tracking executions, and estimating the cost of your function apps.
 
 ## Log and metric types
 
@@ -18,9 +18,9 @@ The Sumo Logic app for Azure Functions app uses the following log and metrics ty
 * **Function Application Logs**. Log generated by the Function App. It includes the logs emitted by the Functions host and logs emitted by customer code. Use these logs to monitor application health, performance, and behavior. For more information on supported metrics, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/functionapplogs).
 * **App Service Authentication Logs**. App Service Authentication Logs are generated for common *Warning* and *Error* logs from the App Service authentication requests. For more information on supported metrics, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/appserviceauthenticationlogs).
 
-To learn more about configuring monitoring for azure functions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-functions/configure-monitoring).
+To learn more about configuring monitoring for Azure functions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-functions/configure-monitoring).
 
-* **Activity logs**, provides insight into any subscription-level or management group level events that have occurred in the Azure. To learn more, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
+* **Activity logs**. Provides insight into any subscription-level or management group level events that have occurred in Azure. To learn more, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
 
 * **Azure Functions specific metrics**. These are metrics specific to Functions like execution count and execution units.
 For more information on supported metrics, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-functions/monitor-functions-reference#azure-functions-specific-metrics).
@@ -45,10 +45,10 @@ When you configure the event hubs source or HTTP source, plan your source catego
 
 ### 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:
+1. Search for the following fields:
    - `tenant_name`. This field is tagged at the collector level and 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 to which the resource name belongs to.
-   - `subscription_id`. ID associated with a subscription where resource is present.
+   - `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.WEB).
    - `resource_type`. Azure resource type (for example, SITES).
@@ -57,7 +57,7 @@ When you configure the event hubs source or HTTP source, plan your source catego
 
 ### Configure Field Extraction Rules
 
-Create a Field Extraction Rule (FER) by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/). If the FER already exists with same name, then skip this step.
+Create a Field Extraction Rule (FER) by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/). If the FER already exists with the same name, then skip this step.
 
 #### Azure Location Extraction FER
 
@@ -123,16 +123,16 @@ resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/*/SITES/* tenant_name=*
 
 ### Configure metrics collection
 
-In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
+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. 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). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
 1. [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 below steps for each Azure Functions that you want to monitor.
-   1. Choose `Stream to an event hub` as destination.
+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 Azure Functions that you want to monitor.
+   1. Choose `Stream to an event hub` as the 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.
-4. 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 Functions app Tag Location" style={{border: '1px solid gray'}} width="400" />
+   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 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.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Functions app Tag Location" style={{border: '1px solid gray'}} width="400" />
 
 ### Configure logs collection
 
@@ -141,11 +141,11 @@ In this section, you will configure a pipeline for shipping metrics from Azure M
 In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) 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/).
-2. To create the **Diagnostic setting** in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the below steps for each Azure Functions that you want to monitor.
+2. To create the **Diagnostic setting** in the 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 Functions that you want to monitor.
    1. Choose `Stream to an event hub` as the destination.
    1. Select `AllMetrics`.
-   1. Use the Event Hub namespace and Event Hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Functions-Configure-Diagnostic-Metrics.png')} alt="Azure Functions app Tag Location" style={{border: '1px solid gray'}} width="800" />
-3. 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 Functions app Tag Location" style={{border: '1px solid gray'}} width="400" />
+   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/integrations/microsoft-azure/Azure-Functions-Configure-Diagnostic-Metrics.png')} alt="Azure Functions app Tag Location" style={{border: '1px solid gray'}} width="800" />
+3. Tag the location field in the source with the right location value.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Functions app Tag Location" style={{border: '1px solid gray'}} width="400" />
 
 #### Activity logs (optional)
 
@@ -165,13 +165,13 @@ For Security events, make sure you enable [Microsoft Defender for Cloud](https:/
 
 ##### Enabling health check metric
 
-For getting health check metric, make sure you enable **Health check** under the **Monitoring** dropdown.
+For getting the health check metric, make sure you enable **Health check** under the **Monitoring** dropdown.
 
 <img src={useBaseUrl('img/integrations/microsoft-azure/Enable-Health-Check-Metric.png')} alt="Enable Health Check Metric" style={{border: '1px solid gray'}} width="800" />
 
 ## Installing the Azure Functions app
 
-This section provides instructions on how to install the Azure Functions app, and shows examples of each of the preconfigured dashboards you can use to analyze your data.
+This section provides instructions on how to install the Azure Functions app and shows examples of each of the preconfigured dashboards you can use to analyze your data.
 
 import AppInstall2 from '../../reuse/apps/app-install-v2.md';
 
@@ -185,7 +185,7 @@ import ViewDashboards from '../../reuse/apps/view-dashboards.md';
 
 ### Overview
 
-The **Azure Functions - Overview** dashboard provides comprehensive information of all the service health incidents or resource health events associated with Azure Functions in your azure account.
+The **Azure Functions - Overview** dashboard provides comprehensive information on all the service health incidents or resource health events associated with Azure Functions in your Azure account.
 
 Use this dashboard to:
 * View recent resource and service health incidents.
@@ -250,7 +250,7 @@ Use this dashboard to:
 
 ### OS Statistics
 
-The **Azure Functions - OS Statistics** dashboard provides information on operating system metrics and statistics relevant to your Azure Functions. This includes details on current assemblies, number of processor threads and other OS-level performance indicators.
+The **Azure Functions - OS Statistics** dashboard provides information on operating system metrics and statistics relevant to your Azure Functions. This includes details on current assemblies, the number of processor threads, and other OS-level performance indicators.
 
 Use this dashboard to:
 * Track OS-level performance metrics impacting your Azure Functions.
@@ -272,7 +272,7 @@ Use this dashboard to:
 
 ### Health
 
-The **Azure Functions - Health** dashboard provides information of any service health incidents or resource health events associated with Azure Functions in your azure account.
+The **Azure Functions - Health** dashboard provides information on any service health incidents or resource health events associated with Azure Functions in your Azure account.
 
 Use this dashboard to:
 * View recent resource and service health incidents.
@@ -282,7 +282,7 @@ Use this dashboard to:
 
 ### Policy and Recommendations
 
-The **Azure Functions - Policy and Recommendations** dashboard provides information of all effect action operations performed by Azure policy and recommendations events from Azure Advisor.
+The **Azure Functions - Policy and Recommendations** dashboard provides information on all effect action operations performed by Azure policy and recommendations events from Azure Advisor.
 
 Use this dashboard to:
 * Monitor policy events with warnings and errors.
@@ -295,11 +295,11 @@ Use this dashboard to:
 
 ### Administrative Operations
 
-The **Azure SQL - Administrative Operations** dashboard provides details on read/write/delete specific changes, different operations used, top 10 operations that caused most errors, and users performing admin operations.
+The **Azure SQL - Administrative Operations** dashboard provides details on read/write/delete specific changes, different operations used, the top 10 operations that caused the most errors, and users performing admin operations.
 
 Use this dashboard to:
 * Identify top users performing administrative operations.
-* View Top 10 operations that caused the most errors.
+* View the Top 10 operations that caused the most errors.
 * View recent read, write, and delete operations.
 
 <img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-Functions/Azure-Functions-Administrative-Operations.png')} alt="Azure Functions Administrative Operations dashboard" style={{border: '1px solid gray'}} width="800" />
