From 4ef0a482d76ab616db5ac2288a8095ddf791d53e Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Tue, 19 Aug 2025 10:35:04 +0530 Subject: [PATCH 1/3] added setup section --- docs/integrations/microsoft-azure/kubernetes.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/integrations/microsoft-azure/kubernetes.md b/docs/integrations/microsoft-azure/kubernetes.md index 44c7fe6947..2640da21bc 100644 --- a/docs/integrations/microsoft-azure/kubernetes.md +++ b/docs/integrations/microsoft-azure/kubernetes.md @@ -41,6 +41,17 @@ The AKS - Control Plane app collects logs for the following [Azure Kubernetes Se For more details on Azure Kubernetes Service logs and metrics, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/aks/monitor-aks-reference). +## Setup + +Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). Sumo Logic supports: + +* 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 Load Balancer 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/AKS/Logs` and `Azure/AKS/Metrics`. + + ### Sample log messages ```json title="kube-audit" From a12f1561488a7bf4ec8a851b49f4d38d1262b106 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Tue, 19 Aug 2025 10:56:17 +0530 Subject: [PATCH 2/3] Update kubernetes.md --- docs/integrations/microsoft-azure/kubernetes.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/integrations/microsoft-azure/kubernetes.md b/docs/integrations/microsoft-azure/kubernetes.md index 2640da21bc..95b9593046 100644 --- a/docs/integrations/microsoft-azure/kubernetes.md +++ b/docs/integrations/microsoft-azure/kubernetes.md @@ -43,15 +43,14 @@ For more details on Azure Kubernetes Service logs and metrics, refer to the [Azu ## Setup -Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). Sumo Logic supports: +Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). -* Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). +* Sumo Logic supports metrics collection using [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). You must explicitly enable diagnostic settings for each Load Balancer 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/AKS/Logs` and `Azure/AKS/Metrics`. - ### Sample log messages ```json title="kube-audit" From e6fb7b8d552a80d0736f3ed5efce01f77d65faac Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Wed, 20 Aug 2025 13:32:36 +0530 Subject: [PATCH 3/3] updated AKS doc --- docs/integrations/microsoft-azure/kubernetes.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/integrations/microsoft-azure/kubernetes.md b/docs/integrations/microsoft-azure/kubernetes.md index 95b9593046..17ab62dce6 100644 --- a/docs/integrations/microsoft-azure/kubernetes.md +++ b/docs/integrations/microsoft-azure/kubernetes.md @@ -45,11 +45,11 @@ For more details on Azure Kubernetes Service logs and metrics, refer to the [Azu Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). -* Sumo Logic supports metrics collection using [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). +You must explicitly enable diagnostic settings for each Kubernetes 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 Load Balancer 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). +Sumo Logic supports metrics collection using [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). -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/AKS/Logs` and `Azure/AKS/Metrics`. +When you configure the Event Hubs source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/AKS/ControlPlane/Logs`. ### Sample log messages @@ -224,10 +224,8 @@ import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; This section walks you through the process of configuring a pipeline to send logs from Azure Monitor to Sumo Logic. 1. To set up the logs collection in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/). - - When you configure the event hubs source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/AKS/ControlPlane/Logs`. - Enable the Kubernetes master node logs in Azure Kubernetes Service to send logs to an event hub created in the previous step. + Enable the Kubernetes master node logs in Azure Kubernetes Service to send logs to an Event Hub. 2. Push logs from Azure Monitor to Event Hub. 1. Sign in to [Azure Portal](https://portal.azure.com/).