Merge pull request #279736 from hangwan97/java_ovew

Update java-overview.md

Author: prmerger-automator[bot]

articles/container-apps/java-overview.md

@@ -6,27 +6,28 @@ author: craigshoemaker
 ms.service: container-apps
 ms.custom: devx-track-extended-java
 ms.topic: conceptual
-ms.date: 04/30/2024
+ms.date: 07/16/2024
 ms.author: cshoe
 ---
 
 # Java on Azure Container Apps overview
 
-Azure Container Apps can run any containerized Java application in the cloud while giving flexible options for how your deploy your applications.
+Azure Container Apps can run any containerized Java application in the cloud while giving flexible options for how you deploy your applications.
 
 When you use Container Apps for your containerized Java applications, you get:
 
 - **Cost effective scaling**: When you use the [Consumption plan](plans.md#consumption), your Java apps can scale to zero. Scaling in when there's little demand for your app automatically drives costs down for your projects.
 
 - **Deployment options**: Azure Container Apps integrates with [Buildpacks](https://buildpacks.io), which allows you to deploy directly from a Maven build, via artifact files, or with your own Dockerfile.
+    - **JAR deployment**: You can deploy your container app directly from a [JAR file](java-get-started.md?tabs=jar).
 
-- **Automatic memory fitting**: Container Apps optimizes how the Java Virtual Machine (JVM) [manages memory](java-memory-fit.md), making the most possible memory available to your Java applications.
+    - **WAR deployment**: You can deploy your container app directly from a [WAR file](java-get-started.md?tabs=war).
 
-- **Build environment variables**: You can configure [custom key-value pairs](java-build-environment-variables.md) to control the Java image build from source code.
+    - **IDE support**: You can deploy your container app directly from [IntelliJ](/azure/developer/java/toolkit-for-intellij/create-container-apps-intellij#deploy-the-container-app).
 
-- **JAR deployment**: You can deploy your container app directly from a [JAR file](java-get-started.md?tabs=jar).
+- **Automatic memory fitting**: Container Apps optimizes how the Java Virtual Machine (JVM) [manages memory](java-memory-fit.md), making the most possible memory available to your Java applications.
 
-- **WAR deployment**: You can deploy your container app directly from a [WAR file](java-get-started.md?tabs=war).
+- **Build environment variables**: You can configure [custom key-value pairs](java-build-environment-variables.md) to control the Java image build from source code.
 
 This article details the information you need to know as you build Java applications on Azure Container Apps.
 
@@ -47,7 +48,7 @@ Running containerized applications usually means you need to create a Dockerfile
 
 Different applications types are implemented either as an individual container app or as a [Container Apps job](jobs.md). Use the following table to help you decide which application type is best for your scenario.
 
-Examples listed in this table aren't meant to be exhaustive, but to help you best understand the intent of different application types.
+Examples listed in this table aren't meant to be exhaustive, but to help your best understand the intent of different application types.
 
 | Type | Examples | Implement as... |
 |--|--|--|
@@ -80,10 +81,18 @@ Keep the following items in mind as you develop your Java applications:
 
 All the [standard observability tools](observability.md) work with your Java application. As you build your Java applications to run on Container Apps, keep in mind the following items:
 
+- **Metrics**: Java Virtual Machine (JVM) metrics are critical for monitoring the health and performance of your Java applications. The data collected includes insights into memory usage, garbage collection, thread count of your JVM. You can check [metrics](java-metrics.md) to help ensure the health and stability of your applications.
+
 - **Logging**: Send application and error messages to `stdout` or `stderror` so they can surface in the log stream. Avoid logging directly to the container's filesystem as is common when using popular logging services.
 
 - **Performance monitoring configuration**: Deploy performance monitoring services as a separate container in your Container Apps environment so it can directly access your application.
 
+## Diagnostics
+
+Azure Container Apps offers built-in diagnostics tools exclusively for Java developers. This support streamlines the debugging and troubleshooting of Java applications running on Azure Container Apps for enhanced efficiency and eases.
+
+- **Dynamic logger level**: Allows you to access and check different level of log details without code modifications or forcing you to restart your app. You can view [Set dynamic logger level](java-dynamic-log-level.md) for reference.
+
 ## Scaling
 
 If you need to make sure requests from your front-end applications reach the same server, or your front-end app is split between multiple containers, make sure to enable [sticky sessions](sticky-sessions.md).
@@ -116,6 +125,8 @@ Azure Container Apps offers support for the following Spring Components as manag
 
 - **Config Server for Spring**: Config Server provides centralized external configuration management for distributed systems. This component designed to address the challenges of [managing configuration settings across multiple microservices](java-config-server-usage.md) in a cloud-native environment.
 
+- **Admin for Spring**： The Admin for Spring managed component provides an administrative interface is designed for Spring Boot web applications that have actuator endpoints. A managed component provides integration and management to your container app by allowing you to bind your container app to the [Admin for Spring component](java-admin.md).
+
 ## Next steps
 
 > [!div class="nextstepaction"]