Uredi

Deli z drugimi prek


Self-diagnose and solve problems in Azure Spring Apps

Note

The Basic, Standard, and Enterprise plans will be deprecated starting from mid-March, 2025, with a 3 year retirement period. We recommend transitioning to Azure Container Apps. For more information, see the Azure Spring Apps retirement announcement.

The Standard consumption and dedicated plan will be deprecated starting September 30, 2024, with a complete shutdown after six months. We recommend transitioning to Azure Container Apps. For more information, see Migrate Azure Spring Apps Standard consumption and dedicated plan to Azure Container Apps.

This article applies to: ✔️ Java ✔️ C#

This article applies to: ✔️ Basic/Standard ✔️ Enterprise

This article shows you how to use Azure Spring Apps diagnostics.

Azure Spring Apps diagnostics is an interactive experience to troubleshoot your app without configuration. Azure Spring Apps diagnostics identifies problems and guides you to information that helps troubleshoot and resolve issues.

Prerequisites

To complete this exercise, you need:

  1. Sign in to the Azure portal.

  2. Go to your Azure Spring Apps Overview page.

  3. Select Diagnose and solve problems in the navigation pane.

    Screenshot of the Azure portal showing the Diagnose and Solve problems page.

Search logged issues

To find an issue, you can either search by typing a keyword or select the solution group to explore all in that category.

Screenshot of the Azure portal showing the Diagnose and Solve problems page with text entered in the search bar.

Selection of Config Server Health Check, Config Server Health Status, or Config Server Update History displays various results.

Note

Spring Cloud Config Server is not applicable to the Azure Spring Apps Enterprise plan.

Screenshot of the Azure portal showing the Availability and Performance page.

Find your target detector and select it to execute. A summary of diagnostics is shown after you execute the detector. Select View details to check diagnostic details.

Screenshot of the Azure portal showing the Availability and Performance page with View details highlighted for a detector.

You can change the diagnostic time range with the controller for CPU Usage. There can be a 15-minute delay for metrics and logs.

Screenshot of the Azure portal showing the Availability and Performance page with the CPU Usage time range selector highlighted.

Some results contain related documentation.

Screenshot of the Azure portal showing the Availability and Performance page with related diagnostic information.

Next steps