Update prometheus-grafana.md

Author: t-vynamani

articles/application-gateway/for-containers/prometheus-grafana.md

@@ -12,16 +12,16 @@ ms.author: greglin
 
 # Configure Application Gateway for Containers for Prometheus and Grafana
 
-Establishing monitoring for Application Gateway for Containers is crutial part of successful operations. Firstly, it allows you to visualize how traffic is controlled, providing actionable insights that help optimize performance and troubleshoot issues promptly. Secondly, monitoring enhances security measures by providing valuable insights during investigations, ensuring that your gateway remains secure and resilient against threats. Implementing monitoring for your Application Gateway for Containers not only supports ongoing performance optimization but also strengthens your overall security posture by enabling proactive detection and response capabilities.
+Establishing monitoring for Application Gateway for Containers is crucial part of successful operations. Firstly, it allows you to visualize how traffic is controlled, providing actionable insights that help optimize performance and troubleshoot issues promptly. Secondly, monitoring enhances security measures by providing valuable insights during investigations, ensuring that your gateway remains secure and resilient against threats. Implementing monitoring for your Application Gateway for Containers not only supports ongoing performance optimization but also strengthens your overall security posture by enabling proactive detection and response capabilities.
 
-You can monitor Azure Application Gateway for Containers resources in the following ways. Refer to the diagram below.
+You can monitor Azure Application Gateway for Containers resources in the following ways. Refer to the diagram.
 - [Backend Health Metrics](../../application-gateway/for-containers/application-gateway-for-containers-metrics.md): ALB Controller's metric and backend health endpoints exposes several metrics and summary of backend health. The metrics endpoint enables exposure to Prometheus.
 
 - [Metrics](../../application-gateway/for-containers/application-gateway-for-containers-metrics.md): Metrics and Activity Logs are exposed through Azure Monitor to monitor the performance of your Application Gateway for Containers deployments. The metrics contain numerical values in an ordered set of time-series data.
 
-- [Diagnostic Logs](../../application-gateway/for-containers/diagnostics.md): Access Logs audit all requests made to Application Gateway for Containers and provides sevreal characteristics, such as the client's IP, requested URL, request/response latencies, return code, and bytes in and out. An access log is collected every 60 seconds.
+- [Diagnostic Logs](../../application-gateway/for-containers/diagnostics.md): Access Logs audit all requests made to Application Gateway for Containers. Logs can provide several characteristics, such as the client's IP, requested URL, request latencies, return code, and bytes in and out. An access log is collected every 60 seconds.
 
-[![A screenshot of architecture grid.](./media/prometheus-grafana/article.drawio.png)](./media/prometheus-grafana/article.drawio.png#lightbox)
+[![A screenshot of architecture grid.](./media/prometheus-grafana/article-drawio.png)](./media/prometheus-grafana/article-drawio.png#lightbox)
 
 ## Learn About the Services
 - [What is Azure Managed Prometheus?](../../azure-monitor/essentials/prometheus-metrics-overview.md)
@@ -53,49 +53,52 @@ You can monitor Azure Application Gateway for Containers resources in the follow
 Complete the steps to configure prometheus and grafana. 
 1. Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
 2. In **Search resources, service, and docs**, type **Application Gateways for Containers** and select your Kubernetes Cluster name.
-    
-    ![A screenshot of kubernetes insights.](./media/prometheus-grafana/configure.png)
-
+   
+   ![[A screenshot of kubernetes insights.](./media/prometheus-grafana/configure.png)](./media/prometheus-grafana/configure.png#lightbox)
+   
 3. Under insights and select **Configure Monitoring**.
+   
     ![A screenshot of monitoring metrics.](./media/prometheus-grafana/grafanacontainer.png)
     Create new instances of Log analytics, Azure Monitor (Prometheus), and Managed Grafana to store current Kubernetes cluster metrics.
 4. In **Search resources, service, and docs**, type **Managed Prometheus** and select.
-    ![A screenshot of Prometheus Managed.](./media/prometheus-grafana/managed-prometheus.png)
+   
+   ![[A screenshot of Prometheus Managed.](./media/prometheus-grafana/managed-prometheus.png)](./media/prometheus-grafana/managed-prometheus.png#lightbox)
+   
 5.  Follow the steps to enable Azure Monitor to enable Managed Prometheus service by selecting **Create**.
-6.  Create Azure Monitor Workspace Instance: 
-    - On the **Create** an Azure Monitor Workspace page, select a subscription and resource group.
-    - Provide a name and a region for the workspace. 
-    - Select **Review + create** to create the workspace. 
+6.  Create Azure Monitor Workspace Instance:
+     1. In the **Create** an Azure Monitor Workspace page, select a subscription and resource group.
+     2. Provide a name and a region for the workspace.
+     3. Select **Review + create** to create the workspace.
 7. Add Prometheus Config Map to your cluster:
-    - Copy this file to notepad or Visual Studio Code:  https://github.com/Azure/prometheus-collector/blob/main/otelcollector/configmaps/ama-metrics-settings-configmap.yaml.
-    - Modify line 35 to set podannotationnamespaceregex  from “ ” to "azure-alb-system".
+   1. Copy this file to notepad or Visual Studio Code:  https://github.com/Azure/prometheus-collector/blob/main/otelcollector/configmaps/ama-metrics-settings-configmap.yaml.
+   2. Modify line 35 to set podannotationnamespaceregex  from “” to "azure-alb-system".
       ```Bash
       # Example Kusto Query
       podannotationnamespaceregex = "azure-alb-system"
       ```
-    - Save the file as configprometheus.yaml.
-    - Add file into CLI (command-line interfaces) under manage files.
-    - Run the following command:
+    3. Save the file as configprometheus.yaml.
+    4. Add file into CLI (command-line interfaces) under manage files.
+    5. Run the following command:
       ```Bash
       # Run the Following Command in Bash
       kubectl apply -f configprometheus.yaml
       ```
- 8. [Create a managed Grafana](../../managed-grafana/quickstart-managed-grafana-portal.md)
- 9. Link a Grafana Workspace:
+8. [Create a managed Grafana](../../managed-grafana/quickstart-managed-grafana-portal.md).
+    Link a Grafana Workspace:
     - In **Search resources, service, and docs**, type **Azure Monitor**.
     - Select your monitor workspace. 
     - Select **Linked Grafana Workspaces**.
      ![A screenshot of Grafana Link.](./media/prometheus-grafana/gwork.png)
-10.  Select a Grafana workspace.
-11.  Select **Link**.
+9. Select a Grafana workspace.
+10. Select **Link**.
 
 
-## Configure AKS cluster for logging
+## Configure Kubernetes cluster for logging
 We created the resources and now we combine all resources and configure prometheus.
 
-1. Cluster Configuration 
-   -  In **Search resources, service, and docs**, search for your kubernetes cluster.
-   -  Search for insights and Select on **Configure Monitoring**.
+1. Cluster configuration 
+   1. In **Search resources, service, and docs**, search for your kubernetes cluster.
+   2. Search for insights and Select on **Configure Monitoring**.
 2. Specify each instance: 
     - Log analytics workspace: Use the default new log analytics workspace created for you.
     - Managed Prometheus: Select on **“Enable Prometheus metrics”** checkbox.
@@ -104,18 +107,19 @@ We created the resources and now we combine all resources and configure promethe
         -   Select on advanced setting: specify the Grafana instance recently created. 
    - Select **“Configure”**.
    > [!NOTE]
-   > Check for ama-metrics under workloads in your kubernetes cluster
-   > ![A screenshot of Checking Config.](./media/prometheus-grafana/notesimage.png)
-
+   > Check for ama-metrics under workloads in your kubernetes cluster.
+   > ![[A screenshot of Checking Config.](./media/prometheus-grafana/notesimage.png)](./media/prometheus-grafana/notesimage.png#lightbox)
+   
 ## Enable diagnostic logs for Application Gateway for Containers
 Activity logging is automatically enabled for every Resource Manager resource. For Access Logs, you must enable access logging to start collecting the data available through those logs. To enable logging, you may configure diagnostic settings in Azure Monitor.
 
 1. [Create a log analytics workspace](../../azure-monitor/logs/quick-create-workspace.md).
 2. Send logs from Application Gateway for Containers to log analytics workspace: 
-    - Enter **Application Gateway for Containers** in the search box. Select your active Application Gateway for Container resource.  
-    - Search and select Diagnostic Setting under Monitoring. Add diagnostic setting.
-    - Select a name, check box **allLogs** which includes the Application Gateway for Container Access Logs, and select **Send to Log analytics Workspace** with your desired subscription and recently made log analytics workspace.
-    ![A screenshot of Application Gateway for Containers Diagnostic Setting.](./media/prometheus-grafana/logsall.png)
+   1. Enter **Application Gateway for Containers** in the search box. Select your active Application Gateway for Container resource.
+   2. Search and select Diagnostic Setting under Monitoring. Add diagnostic setting.
+   3. Select a name, check box **allLogs** which includes the Application Gateway for Container Access Logs, and select **Send to Log analytics Workspace** with your desired subscription and recently made log analytics workspace.
+   ![[A screenshot of Application Gateway for Containers Diagnostic Setting.](./media/prometheus-grafana/logsall.png)](./media/prometheus-grafana/logsall.png#lightbox)
+
 3. Select **Save**.
 
 ## Access Grafana dashboard
@@ -126,8 +130,8 @@ In this section, we enter Grafana default dashboards.
 3. Select on Endpoint URL in the overview.
    ![A screenshot of Grafana Endpoint.](./media/prometheus-grafana/grafaend.png)
 
-5. After entering your user credentials, refer to the Grafana introduction.
-6. Select on the left side bar to access default dashboards under dashboards.
+4. After entering your user credentials, refer to the Grafana introduction.
+5. Select on the left side bar to access default dashboards under dashboards.
    ![A screenshot of Dafault Grafana Dashboard.](./media/prometheus-grafana/grafana-default.png)
 
 ## Graph Prometheus metrics on Grafana 
@@ -138,14 +142,13 @@ In this section, we visualize a sample metric from Prometheus metrics. Refer to
 2. Select **Add Visualization**.
 3. Search for prometheus under data source.
 ![A screenshot of Data Source Prometheus Dashboard.](./media/prometheus-grafana/data-source-prometheus.png)
-4. Select desired metric. For Example: alb_controller_total_unhealthy_endpoints which gives any unhealthy endpoints of your backend service.
+4. Select desired metric. For Example: alb_controller_total_unhealthy_endpoints that gives any unhealthy endpoints of your backend service.
 5. Choose app as alb-controller.
 6. Select name of the panel, type of visualization, and time range.
    ![A screenshot of Prometheus Logging Test.](./media/prometheus-grafana/prometheus-grafana-viewing.png)
-
-8. **Save + Apply** of your panel to add into your dashboard.
+7. **Save + Apply** of your panel to add into your dashboard.
    > [!NOTE]
-   > Add a custom legend by {{variable_name}}
+   > Add a custom legend by {{variable_name}}.
 
 ## Graph access logs and metrics on Grafana
 
@@ -159,11 +162,11 @@ In this section, we visualize a sample logs from Log Analytics Workspace. Refer
 ![A screenshot of Log Data Source.](./media/prometheus-grafana/log-data-source.png)
 4. Change service as **Logs**.
 5. Type: 
-```kusto
-// Example Kusto Query
-AGCAccessLogs
-| project BackendResponseLatency, TimeGenerated
-```
+  ```kusto
+  // Example Kusto Query
+  AGCAccessLogs
+  | project BackendResponseLatency, TimeGenerated
+  ```
 6. Select a **Time Series** as a visualization.
 7. Select name, description, and time range of the panel.
 ![A screenshot of Application Gateway for Containers Logging Example.](./media/prometheus-grafana/logging-example.png)
@@ -175,11 +178,11 @@ AGCAccessLogs
 2. Select **Add Visualization**.
 3. Search for Azure Monitor under data source+ **Add**.
 4. Change service as Metrics.
-5. Select your application gateway for containers instance. 
-![A screenshot of Metrics Log Data Source.](./media/prometheus-grafana/metrics-logs-datasource.png)
+5. Select your application gateway for containers instance.
+![[A screenshot of Metrics Log Data Source.](./media/prometheus-grafana/metrics-logs-datasource.png)](./media/prometheus-grafana/metrics-logs-datasource.png#lightbox)
 6. Select metric namespace as microsoft.servicenetworking/trafficcontrollers.
 7. Choose a metric such as **total requests** and type of data visualization.
-![A screenshot of Example Metrics Log Data Source.](./media/prometheus-grafana/metrics-logs.png)
+![[A screenshot of Example Metrics Log Data Source.](./media/prometheus-grafana/metrics-logs.png)](./media/prometheus-grafana/metrics-logs.png#lightbox)
 8. Select a name, description, and time range of the panel.
 9. **Save + Apply** to your dashboard.