Merge pull request #249190 from bwren/docs-editor/monitor-kubernetes-1692834847

Update monitor-kubernetes.md

Author: prmerger-automator[bot]

articles/azure-monitor/containers/monitor-kubernetes.md

@@ -61,7 +61,7 @@ The following table lists the services that are commonly used by the network eng
 Following are common scenarios for monitoring the network.
 
 - Create [flow logs](../../network-watcher/network-watcher-nsg-flow-logging-overview.md) to log information about the IP traffic flowing through network security groups used by your cluster and then use [traffic analytics](../../network-watcher/traffic-analytics.md) to analyze and provide insights on this data. You'll most likely use the same Log Analytics workspace for traffic analytics that you use for Container insights and your control plane logs.
-- Using traffic analytics, you can determine if any traffic is flowing either to or from any unexpected ports used by the cluster and also if any traffic is flowing over public IPs that shouldn't be exposed. Use this information to determine whether your network rules need modification.
+- Using [traffic analytics](../../network-watcher/traffic-analytics.md), you can determine if any traffic is flowing either to or from any unexpected ports used by the cluster and also if any traffic is flowing over public IPs that shouldn't be exposed. Use this information to determine whether your network rules need modification.
 
 
 ## Platform engineer
@@ -229,7 +229,6 @@ Following are common scenarios for monitoring your managed Kubernetes components
 **Troubleshooting**<br>
 - For troubleshooting scenarios, you can access kubelet logs using the process described at [Get kubelet logs from Azure Kubernetes Service (AKS) cluster nodes](../../aks/kubelet-logs.md).
 
-
 ### Monitor level 4 - Kubernetes objects and workloads
 
 The Kubernetes objects and workloads level includes the following components:
@@ -243,6 +242,7 @@ The Kubernetes objects and workloads level includes the following components:
 Following are common scenarios for monitoring your Kubernetes objects and workloads.
 
 
+
 **Container insights**<br>
 - Use the **Nodes** and **Controllers** views to see the health and performance of the pods running on them and drill down to the health and performance of their containers.
 - Use the **Containers** view to see the health and performance for the containers. For more information on analyzing container health and performance, see [Monitor your Kubernetes cluster performance with Container Insights](container-insights-analyze.md#analyze-nodes-controllers-and-container-health).
@@ -251,11 +251,9 @@ Following are common scenarios for monitoring your Kubernetes objects and worklo
 **Grafana dashboards**<br>
 - Multiple [Kubernetes dashboards](https://grafana.com/grafana/dashboards/?search=kubernetes) are available that visualize the performance and health of your nodes based on data stored in Prometheus.
 
-
 **Live data**
 - In troubleshooting scenarios, Container Insights provides access to live AKS container logs (stdout/stderror), events and pod metrics. For more information about this feature, see [How to view Kubernetes logs, events, and pod metrics in real-time](container-insights-livedata-overview.md).
 
-
 ### Alerts for the platform engineer
 
 [Alerts in Azure Monitor](..//alerts/alerts-overview.md) proactively notify you of interesting data and patterns in your monitoring data. They allow you to identify and address issues in your system before your customers notice them. If you have an existing [ITSM solution](../alerts/itsmc-overview.md) for alerting, you can [integrate it with Azure Monitor](../alerts/itsmc-overview.md). You can also [export workspace data](../logs/logs-data-export.md) to send data from your Log Analytics workspace to another location that supports your current alerting solution.
@@ -283,18 +281,21 @@ In addition to developing the application, the *developer* maintains the applica
 The following table lists the services that are commonly used by the developer to monitor the health and performance of the Kubernetes cluster and its components.  
 
 
+
 | Service | Description |
 |:---|:---|
 | [Application insights](../app/app-insights-overview.md) |  Feature of Azure Monitor that provides application performance monitoring (APM) to monitor applications running on your Kubernetes cluster from development, through test, and into production. Quickly identify and mitigate latency and reliability issues using distributed traces. Supports [OpenTelemetry](../app/opentelemetry-overview.md#opentelemetry) for vendor-neutral instrumentation. |
 
 
+
 See [Data Collection Basics of Azure Monitor Application Insights](../app/opentelemetry-overview.md) for options on configuring data collection from the application running on your cluster and decision criteria on the best method for your particular requirements. 
 
 ### Monitor level 5 - Application
 
 Following are common scenarios for monitoring your application.
 
 
+
 **Application performance**<br>
 - Use the **Performance** view in Application insights to view the performance of different operations in your application.
 - Use [Profiler](../profiler/profiler-overview.md) to capture and view performance traces for your application.
@@ -317,8 +318,8 @@ Following are common scenarios for monitoring your application.
 
 - For AKS clusters, deploy the [Istio-based service mesh add-on](../../aks/istio-about.md) which provides observability to your microservices architecture. [Istio](https://istio.io/) is an open-source service mesh that layers transparently onto existing distributed applications. The add-on assists in the deployment and management of Istio for AKS.
 
-
 ## See also
 
 - See [Monitoring AKS](../../aks/monitor-aks.md) for guidance on monitoring specific to Azure Kubernetes Service (AKS).
 
+