Skip to content

Commit e6b1f8a

Browse files
authored
Update aks-diagnostics.md
Updated: 1) alt text with description 2) alt text end with a period 3) Line 48 corrected "gether" to "gather" 4) unified the term to "AKS Diagnose and Solve Problems"
1 parent bb26bd2 commit e6b1f8a

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

articles/aks/aks-diagnostics.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Kubernetes Service (AKS) Diagnostics Overview
2+
title: Azure Kubernetes Service (AKS) Diagnose and Solve Problems Overview
33
description: Learn about self-diagnosing clusters in Azure Kubernetes Service.
44
services: container-service
55
author: rongzhang
@@ -8,24 +8,24 @@ ms.date: 03/10/2023
88
ms.author: rongzhang
99
---
1010

11-
# Azure Kubernetes Service Diagnostics overview
11+
# Azure Kubernetes Service Diagnose and Solve Problems overview
1212

13-
Troubleshooting Azure Kubernetes Service (AKS) cluster issues plays an important role in maintaining your cluster, especially if your cluster is running mission-critical workloads. AKS Diagnostics is an intelligent, self-diagnostic experience that:
13+
Troubleshooting Azure Kubernetes Service (AKS) cluster issues plays an important role in maintaining your cluster, especially if your cluster is running mission-critical workloads. AKS Diagnose and Solve Problems is an intelligent, self-diagnostic experience that:
1414
* Helps you identify and resolve problems in your cluster.
1515
* Requires no extra configuration or billing cost.
1616

1717

18-
## Open AKS Diagnostics
18+
## Open AKS Diagnose and Solve Problems
1919

20-
To access AKS Diagnostics:
20+
To access AKS Diagnose and Solve Problems:
2121

2222
1. Navigate to your Kubernetes cluster in the [Azure portal](https://portal.azure.com).
23-
2. Click on **Diagnose and solve problems** in the left navigation, which opens AKS Diagnostics.
23+
2. Click on **Diagnose and solve problems** in the left navigation, which opens AKS Diagnose and Solve Problems.
2424
3. Choose a category that best describes the issue of your cluster by:
2525
* Referring the keywords in each tile description on the homepage.
2626
* Typing a keyword that best describes your issue in the search bar.
2727

28-
![Homepage](./media/concepts-diagnostics/aks-diagnostics-homepage.PNG)
28+
![screenshot of AKS Diagnose and Solve Problems Homepage.](./media/concepts-diagnostics/aks-diagnostics-homepage.PNG)
2929

3030

3131
## View a diagnostic report
@@ -43,29 +43,29 @@ Based on the outcome, you may follow the detailed instructions or peruse the doc
4343

4444
**Example scenario 1**: I observed that my application is getting disconnected or experiencing intermittent connection issues. In response, I click **Connectivity Issues** tile to investigate the potential causes.
4545

46-
![AKS Diagnostics Results - Networking Tile](./media/concepts-diagnostics/aks-diagnostics-tile.png)
46+
![screenshot of AKS Diagnose and solve problems Results - Networking Tile.](./media/concepts-diagnostics/aks-diagnostics-tile.png)
4747

48-
I received a diagnostic alert indicating that the disconnection may be related to my *Cluster DNS*. To gether more information, I clicked on *View details*.
48+
I received a diagnostic alert indicating that the disconnection may be related to my *Cluster DNS*. To gather more information, I clicked on *View details*.
4949

50-
![AKS Diagnostics Results - Networking](./media/concepts-diagnostics/aks-diagnostics-results.png)
50+
![Screenshot of AKS Diagnose and solve problems - Networking.](./media/concepts-diagnostics/aks-diagnostics-results.png)
5151

5252
Based on the diagnostic result, it appears that the issue may be related to known DNS issues or VNET configuration. Thankfully, I can use the documentation links provided to address the issue and resolve the problem.
5353

54-
![AKS Diagnostics Results - Networking - Cluster DNS](./media/concepts-diagnostics/aks-diagnostics-network.png)
54+
![AKS Diagnose and Solve Problems Results - Networking - Cluster DNS.](./media/concepts-diagnostics/aks-diagnostics-network.png)
5555

5656
Furthermore, if the recommended documentation based on the diagnostic results does not resolve the issue, you can return to the previous step in Diagnostics and refer to additional documentation.
5757

58-
![AKS Diagnostics Results - Additional - Docs](./media/concepts-diagnostics/aks-diagnostics-doc.png)
58+
![Screenshot of AKS Diagnose and solve problem result - Additional - Docs.](./media/concepts-diagnostics/aks-diagnostics-doc.png)
5959

60-
## Use Diagnostics for Best Practices
60+
## Use AKS Diagnose and Solve Problems for Best Practices
6161

62-
Deploying applications on AKS requires adherence to best practices to guarantee optimal performance, availability, and security. To this end, the AKS Diagnostics **Best Practices** tile provides an array of best practices that can assist in managing various aspects such as VM resource provisioning, cluster upgrades, scaling operations, subnet configuration, and other essential aspects of a cluster's configuration. Leveraging the AKS Diagnostics can be vital in ensuring that your cluster adheres to best practices and that any potential issues are identified and resolved in a timely and effective manner. By incorporating AKS Diagnostics into your operational practices, you can be confident in the reliability and security of your application in production.
62+
Deploying applications on AKS requires adherence to best practices to guarantee optimal performance, availability, and security. To this end, the AKS Diagnose and Solve Problems **Best Practices** tile provides an array of best practices that can assist in managing various aspects such as VM resource provisioning, cluster upgrades, scaling operations, subnet configuration, and other essential aspects of a cluster's configuration. Leveraging the AKS Diagnose and Solve Problems can be vital in ensuring that your cluster adheres to best practices and that any potential issues are identified and resolved in a timely and effective manner. By incorporating AKS Diagnose and Solve Problems into your operational practices, you can be confident in the reliability and security of your application in production.
6363

6464
**Example Scenario 2**: My cluster seems to be in good health. All nodes are ready, and my application runs without any issues. However, I am curious about the best practices I can follow to prevent potential problems. So, I click on the **Best Practices** tile. After reviewing the recommendations, I discovered that even though my cluster appears healthy at the moment, there are still some things I can do to avoid latency, throttling or VM uptime issues in the future.
6565

66-
![AKS Diagnostics Results - Best - Practice](./media/concepts-diagnostics/aks-diagnostics-best.png)
66+
![Screenshot of AKS Diagnose and solve problem - Best - Practice.](./media/concepts-diagnostics/aks-diagnostics-best.png)
6767

68-
![AKS Diagnostics Results - Best - result](./media/concepts-diagnostics/aks-diagnostics-practice.png)
68+
![Screenshot of AKS Diagnose and solve problem - Best - result.](./media/concepts-diagnostics/aks-diagnostics-practice.png)
6969

7070
## Next steps
7171

0 commit comments

Comments
 (0)