Merge pull request #212508 from trask/spring-yaml

Spring Boot updates

Author: liljack17

articles/azure-monitor/app/java-spring-boot.md

@@ -7,13 +7,11 @@ ms.devlang: java
 ms.custom: devx-track-java
 ---
 
-# Configure Azure Monitor Application Insights for Spring Boot
+# Using Azure Monitor Application Insights with Spring Boot
 
-You can enable the Azure Monitor Application Insights agent for Java by adding an argument to the JVM. When you can't do this, you can use a programmatic configuration. We detail these two configurations below. 
+There are two options for enabling Application Insights Java with Spring Boot: JVM argument and programmatically.
 
-## Addition of a JVM argument 
-
-### Usual case
+## Enabling with JVM argument 
 
 Add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.4.1.jar"` somewhere before `-jar`, for example:
 
@@ -35,9 +33,14 @@ If you're using the *shell* form, add the JVM arg `-javaagent:"path/to/applicati
 ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.4.1.jar" -jar <myapp.jar>
 ```
 
-## Programmatic configuration
+### Configuration
+
+See [configuration options](./java-standalone-config.md).
+
+## Enabling programmatically
+
+To enable Application Insights Java programmatically, you must add the following dependency:
 
-To use the programmatic configuration and attach the Application Insights agent for Java during the application startup, you must add the following dependency.
 ```xml
 <dependency>
     <groupId>com.microsoft.azure</groupId>
@@ -46,7 +49,8 @@ To use the programmatic configuration and attach the Application Insights agent
 </dependency>
 ```
 
-And invoke the `attach()` method of the `com.microsoft.applicationinsights.attach.ApplicationInsights` class.
+And invoke the `attach()` method of the `com.microsoft.applicationinsights.attach.ApplicationInsights` class
+in the first line of your `main()` method.
 
 > [!WARNING]
 > 
@@ -58,7 +62,7 @@ And invoke the `attach()` method of the `com.microsoft.applicationinsights.attac
 
 > [!WARNING]
 > 
-> The invocation must be requested at the beginning of the `main` method.
+> The invocation must be at the beginning of the `main` method.
 
 Example:
 
@@ -73,10 +77,26 @@ public class SpringBootApp {
 }
 ```
 
-If you want to use a JSON configuration: 
-* The `applicationinsights.json` file has to be in the classpath
-* Or you can use an environmental variable or a system property, more in the _Configuration file path_ part on [this page](../app/java-standalone-config.md). Spring properties defined in a Spring _.properties_ file are not supported.
+### Configuration
+
+> [!NOTE]
+> Spring's `application.properties` or `application.yaml` files are not supported as
+> as sources for Application Insights Java configuration.
+
+Programmatic enablement supports all the same [configuration options](./java-standalone-config.md)
+as the JVM argument enablement, with the following differences below.
+
+#### Configuration file location
+
+By default, when enabling Application Insights Java programmatically, the configuration file `applicationinsights.json`
+will be read from the classpath.
+
+See [configuration file path configuration options](./java-standalone-config.md#configuration-file-path)
+to change this location.
+
+#### Self-diagnostic log file location
 
+By default, when enabling Application Insights Java programmatically, the `applicationinsights.log` file containing
+the agent logs will be located in the directory from where the JVM is launched (user directory).
 
-> [!TIP]
-> With a programmatic configuration, the `applicationinsights.log` file containing the agent logs is located in the directory from where the JVM is launched (user directory). This default behavior can be changed (see the _Self-diagnostics_ part of [this page](../app/java-standalone-config.md)).
+See [self-diagnostic configuration options](./java-standalone-config.md#self-diagnostics) to change this location.