From 23c37829e6e65f33ae343ec70d2c31ba14d30153 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Tue, 13 May 2025 18:38:03 +0530 Subject: [PATCH 1/6] Updated Azure docs --- .../azure-container-instances.md | 101 +++--------------- .../microsoft-azure/kubernetes.md | 76 +++---------- 2 files changed, 27 insertions(+), 150 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index d6a0ab359d..f4f37bfc9f 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -24,100 +24,15 @@ For more information on supported dimensions, refer to the [Azure documentation] ## Setup * Set up application logs collection using fluent-bit sidecar container using the [http output plugin](https://docs.fluentbit.io/manual/1.5/pipeline/outputs/http) and the [tail input plugin](https://docs.fluentbit.io/manual/1.5/pipeline/inputs/tail). You must explicitly enable fluent-bit collection for each container group which you want to monitor. -* Set up metrics collection using Azure Metrics Source. +* Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). :::note Sumo Logic Metrics source is currently in Beta, to participate, contact your Sumo Logic account executive. ::: - -### 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**.
[**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 the following fields: - - `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 to which 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 a Azure resource. - - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances service is Subscriptions). -1. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields). - -### Configure field extraction rules - -Create the following Field Extraction Rule(s) (FER) for Azure Storage by following the instructions in [Create a Field Extraction Rule](/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/(?[^/]+)" nodrop - | parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop - | parse regex field=resourceId "/PROVIDERS/(?[^/]+)" nodrop - | parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?[^/]+)/(?.+)" nodrop - | parse regex field=resource_name "(?[^/]+)(?:/PROVIDERS/[^/]+)?/(?[^/]+)/?(?.+)" 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 - -Create the following metrics rules by following the instructions in [Create a metrics rule](/docs/metrics/metric-rules-editor/#create-a-metrics-rule). - -#### Azure observability metadata extraction container instance level - - ```sql - Rule Name: AzureObservabilityMetadataExtractionAzureContainerInstanceLevel - ``` - - ```sql title="Metric match expression" - resourceId=resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/MICROSOFT.CONTAINERINSTANCE/*/* tenant_name=* - ``` - | Fields extracted | Metric rule | - |:------------------|:----------------------------| - | subscription_id | $resourceId._1 | - | resource_group | $resourceId._2 | - | provider_name | MICROSOFT.CONTAINERINSTANCE | - | resource_type | $resourceId._3 | - | resource_name | $resourceId._4 | ### Configure metrics collection -:::note -Sumo Logic Metrics source is currently in Beta, to participate, contact your Sumo Logic account executive. -::: - -In the Sumo Logic Azure Metrics source configuration, - -- To set up the Azure Metrics source in Sumo Logic, refer to the shared beta documentation. -- Configure namespaces as `Microsoft.ContainerInstance/containerGroups`.
Azure Container Instance Namespaces +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 @@ -170,6 +85,18 @@ import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2 +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 to which 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 a 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 Container Instances dashboards import ViewDashboards from '../../reuse/apps/view-dashboards.md'; diff --git a/docs/integrations/microsoft-azure/kubernetes.md b/docs/integrations/microsoft-azure/kubernetes.md index 66a803d552..6ce5fc175f 100644 --- a/docs/integrations/microsoft-azure/kubernetes.md +++ b/docs/integrations/microsoft-azure/kubernetes.md @@ -37,63 +37,6 @@ The AKS - Control Plane app collects logs for the following [Azure Kubernetes Se * **kube-controller-manager**. The Controller Manager oversees a number of smaller controllers that perform actions, such as replicating pods and handling node operations. * **cluster-autoscaler**. The cluster autoscaler component watches for pods in your cluster that can't be scheduled because of resource constraints. When the cluster autoscaler detects issues, it scales up the number of nodes in the node pool to meet the application demands. It also regularly checks nodes for a lack of running pods and scales down the number of nodes as needed. -### 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**.
[**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 the following fields: - - `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 to which 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 a Azure resource. - - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Kubernetes service is Subscriptions). -1. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields). - -### Configure field extraction rules - -Create the following Field Extraction Rule(s) (FER) for Azure Kubernetes Service by following the instructions in [Create a Field Extraction Rule](/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/(?[^/]+)" nodrop - | parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop - | parse regex field=resourceId "/PROVIDERS/(?[^/]+)" nodrop - | parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?[^/]+)/(?.+)" nodrop - | parse regex field=resource_name "(?[^/]+)(?:/PROVIDERS/[^/]+)?/(?[^/]+)/?(?.+)" 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 - ``` - ### Sample log messages ```json title="kube-audit" @@ -254,12 +197,7 @@ tenant_name={{tenant_name}} subscription_id={{subscription_id}} resource_group={ ### Configure metrics collection -:::note -Sumo Logic Metrics source is currently in Beta, to participate, contact your Sumo Logic account executive. -::: - -- To set up the Azure Metrics source in Sumo Logic, refer to the shared beta documentation. -- Configure the namespaces as `Microsoft.ContainerService/managedClusters`, `microsoft.kubernetes/connectedClusters`, `microsoft.kubernetesconfiguration/extensions`, and `microsoft.hybridcontainerservice/provisionedClusters`.
Azure Container Instance Namespaces +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). ### Collecting logs for the Azure Kubernetes Cluster @@ -294,6 +232,18 @@ import AppInstall from '../../reuse/apps/app-install.md'; +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 to which 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 a 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 Kubernetes Service dashboards ### Overview From 2233156b5d01154ec5a043f05490470a0cea47d3 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Tue, 13 May 2025 18:59:43 +0530 Subject: [PATCH 2/6] added monitors section --- .../microsoft-azure/azure-container-instances.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index f4f37bfc9f..a9292bf28a 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -141,6 +141,14 @@ Use this dashboard to: Azure Container Instances - Policy and Recommendations +### Azure Container Instances alerts +These alerts are metric based and will work for all Azure Container Instances. + +| Alert Name | Alert Description and Conditions | Alert Condition | Recover Condition | +|:----------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:---------------------| +| `Azure Container Instances - Memory Usage` | This alert is triggered when Memory Usage is greater than 20MB. Also warning alert is triggered when Memory Usage is greater than 15MB | data volume > 20MB | data volume <= 20MB | +| `Azure Container Instances - Cpu Usage` | This alert is triggered when Cpu Usage is greater than 100milicore. Also warning alert is triggered when Cpu Usage is greater than 90milicore | milicores > 100 | milicores <= 100 | + ## Troubleshooting ### HTTP Logs and Metrics Source used by Azure Functions From 0800658e2b032273f749e894867c1cd5c0540c86 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Tue, 13 May 2025 21:01:14 +0530 Subject: [PATCH 3/6] resolved syntax issue --- .../integrations/microsoft-azure/azure-container-instances.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index a9292bf28a..d824be5a84 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -146,8 +146,8 @@ These alerts are metric based and will work for all Azure Container Instances. | Alert Name | Alert Description and Conditions | Alert Condition | Recover Condition | |:----------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:---------------------| -| `Azure Container Instances - Memory Usage` | This alert is triggered when Memory Usage is greater than 20MB. Also warning alert is triggered when Memory Usage is greater than 15MB | data volume > 20MB | data volume <= 20MB | -| `Azure Container Instances - Cpu Usage` | This alert is triggered when Cpu Usage is greater than 100milicore. Also warning alert is triggered when Cpu Usage is greater than 90milicore | milicores > 100 | milicores <= 100 | +| `Azure Container Instances - Memory Usage` | This alert is triggered when Memory Usage is greater than 20MB. Also warning alert is triggered when Memory Usage is greater than 15MB | data volume > 20MB | data volume < = 20MB | +| `Azure Container Instances - Cpu Usage` | This alert is triggered when Cpu Usage is greater than 100milicore. Also warning alert is triggered when Cpu Usage is greater than 90milicore | milicores > 100 | milicores < = 100 | ## Troubleshooting From 8f2ad0491998aeecf633fc3c12bf8a9ea037733f Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Tue, 13 May 2025 21:32:13 +0530 Subject: [PATCH 4/6] Update azure-container-instances.md --- .../microsoft-azure/azure-container-instances.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index d824be5a84..ff65347da0 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -142,12 +142,13 @@ Use this dashboard to: Azure Container Instances - Policy and Recommendations ### Azure Container Instances alerts + These alerts are metric based and will work for all Azure Container Instances. -| Alert Name | Alert Description and Conditions | Alert Condition | Recover Condition | -|:----------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:---------------------| -| `Azure Container Instances - Memory Usage` | This alert is triggered when Memory Usage is greater than 20MB. Also warning alert is triggered when Memory Usage is greater than 15MB | data volume > 20MB | data volume < = 20MB | -| `Azure Container Instances - Cpu Usage` | This alert is triggered when Cpu Usage is greater than 100milicore. Also warning alert is triggered when Cpu Usage is greater than 90milicore | milicores > 100 | milicores < = 100 | +| Alert Name | Description | Alert Condition | Recover Condition | +|:-- |:-- |:--|:-- | +| `Azure Container Instances - Memory Usage` | This alert is triggered when memory usage is greater than 20 MB. Also warning alert is triggered when the memory usage exceeds 15 MB. | Data volume > 20MB | Data volume <= 20MB | +| `Azure Container Instances - CPU Usage` | This alert is triggered when CPU usage is greater than 100 milicore. Also warning alert is triggered when the CPU usage exceeds 90 milicore. | milicores > 100 | milicores <= 100 | ## Troubleshooting From e13a0fe231ecf562c40a6264a39025bfcc7d6e25 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Wed, 14 May 2025 10:14:19 +0530 Subject: [PATCH 5/6] resolved syntax issue --- .../microsoft-azure/azure-container-instances.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index ff65347da0..b35f8aa33a 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -145,10 +145,10 @@ Use this dashboard to: These alerts are metric based and will work for all Azure Container Instances. -| Alert Name | Description | Alert Condition | Recover Condition | -|:-- |:-- |:--|:-- | -| `Azure Container Instances - Memory Usage` | This alert is triggered when memory usage is greater than 20 MB. Also warning alert is triggered when the memory usage exceeds 15 MB. | Data volume > 20MB | Data volume <= 20MB | -| `Azure Container Instances - CPU Usage` | This alert is triggered when CPU usage is greater than 100 milicore. Also warning alert is triggered when the CPU usage exceeds 90 milicore. | milicores > 100 | milicores <= 100 | +| Alert Name | Description | Alert Condition | Recover Condition | +|:-- |:-- |:--|:---------------------| +| `Azure Container Instances - Memory Usage` | This alert is triggered when memory usage is greater than 20 MB. Also warning alert is triggered when the memory usage exceeds 15 MB. | Data volume > 20MB | Data volume < = 20MB | +| `Azure Container Instances - CPU Usage` | This alert is triggered when CPU usage is greater than 100 milicore. Also warning alert is triggered when the CPU usage exceeds 90 milicore. | milicores > 100 | milicores < = 100 | ## Troubleshooting From db1c962db58abc1ab9728ec5d6b63a9c5635f99a Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Wed, 14 May 2025 10:34:45 +0530 Subject: [PATCH 6/6] Update azure-container-instances.md --- docs/integrations/microsoft-azure/azure-container-instances.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index b35f8aa33a..a672e32177 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -148,7 +148,7 @@ These alerts are metric based and will work for all Azure Container Instances. | Alert Name | Description | Alert Condition | Recover Condition | |:-- |:-- |:--|:---------------------| | `Azure Container Instances - Memory Usage` | This alert is triggered when memory usage is greater than 20 MB. Also warning alert is triggered when the memory usage exceeds 15 MB. | Data volume > 20MB | Data volume < = 20MB | -| `Azure Container Instances - CPU Usage` | This alert is triggered when CPU usage is greater than 100 milicore. Also warning alert is triggered when the CPU usage exceeds 90 milicore. | milicores > 100 | milicores < = 100 | +| `Azure Container Instances - CPU Usage` | This alert is triggered when CPU usage is greater than 100 milicore. Also warning alert is triggered when the CPU usage exceeds 90 millicore. | millicores > 100 | millicores < = 100 | ## Troubleshooting