You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/java-2x-agent.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ If you have [instrumented your Java web app with Application Insights SDK][java]
34
34
To use the Java agent, you install it on your server. Your web apps must be instrumented with the [Application Insights Java SDK][java].
35
35
36
36
## Install the Application Insights agent for Java
37
-
1. On the machine running your Java server, [download the 2.x agent](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/2.6.2). Please make sure the version of the 2.x Java Agent that you use matches the version of the 2.x Application Insights Java SDK that you use.
37
+
1. On the machine running your Java server, [download the 2.x agent](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/2.6.4). Please make sure the version of the 2.x Java Agent that you use matches the version of the 2.x Application Insights Java SDK that you use.
38
38
2. Edit the application server startup script, and add the following JVM argument:
39
39
40
40
`-javaagent:<full path to the agent JAR file>`
@@ -87,7 +87,7 @@ For Azure App Services, do the following:
The agent must be packaged as a resource in your project such that it ends up in the D:/home/site/wwwroot/ directory. You can confirm that your agent is in the correct App Service directory by going to **Development Tools** > **Advanced Tools** > **Debug Console** and examining the contents of the site directory.
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/java-2x-troubleshoot.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Questions or problems with [Azure Application Insights in Java][java]? Here are
20
20
## Build errors
21
21
**In Eclipse or Intellij Idea, when adding the Application Insights SDK via Maven or Gradle, I get build or checksum validation errors.**
22
22
23
-
* If the dependency `<version>` element is using a pattern with wildcard characters (e.g. (Maven) `<version>[2.0,)</version>` or (Gradle) `version:'2.+'`), try specifying a specific version instead like `2.6.2`.
23
+
* If the dependency `<version>` element is using a pattern with wildcard characters (e.g. (Maven) `<version>[2.0,)</version>` or (Gradle) `version:'2.+'`), try specifying a specific version instead like `2.6.4`.
24
24
25
25
## No data
26
26
**I added Application Insights successfully and ran my app, but I've never seen data in the portal.**
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/java-in-process-agent.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ This section shows you how to download the auto-instrumentation jar file.
28
28
29
29
#### Download the jar file
30
30
31
-
Download the [applicationinsights-agent-3.2.3.jar](https://github.com/microsoft/ApplicationInsights-Java/releases/download/3.2.3/applicationinsights-agent-3.2.3.jar) file.
31
+
Download the [applicationinsights-agent-3.2.4.jar](https://github.com/microsoft/ApplicationInsights-Java/releases/download/3.2.4/applicationinsights-agent-3.2.4.jar) file.
32
32
33
33
> [!WARNING]
34
34
>
@@ -50,7 +50,7 @@ Download the [applicationinsights-agent-3.2.3.jar](https://github.com/microsoft/
50
50
51
51
#### Point the JVM to the jar file
52
52
53
-
Add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to your application's JVM args.
53
+
Add `-javaagent:path/to/applicationinsights-agent-3.2.4.jar` to your application's JVM args.
54
54
55
55
> [!TIP]
56
56
> For help with configuring your application's JVM args, see [Tips for updating your JVM args](./java-standalone-arguments.md).
@@ -65,7 +65,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to your application
- Or you can create a configuration file named `applicationinsights.json`. Place it in the same directory as `applicationinsights-agent-3.2.3.jar` with the following content:
68
+
- Or you can create a configuration file named `applicationinsights.json`. Place it in the same directory as `applicationinsights-agent-3.2.4.jar` with the following content:
69
69
70
70
```json
71
71
{
@@ -357,13 +357,13 @@ If you want to attach custom dimensions to your logs, use [Log4j 1.2 MDC](https:
357
357
358
358
### Send custom telemetry by using the 2.x SDK
359
359
360
-
1. Add `applicationinsights-core-2.6.3.jar` to your application. All 2.x versions are supported by Application Insights Java 3.x. If you have a choice. it's worth using the latest version:
360
+
1. Add `applicationinsights-core-2.6.4.jar` to your application. All 2.x versions are supported by Application Insights Java 3.x. If you have a choice. it's worth using the latest version:
If you are using the *exec* form, add the parameter `"-javaagent:path/to/applicationinsights-agent-3.2.3.jar"` to the parameter list somewhere before the `"-jar"` parameter, for example:
27
+
If you are using the *exec* form, add the parameter `"-javaagent:path/to/applicationinsights-agent-3.2.4.jar"` to the parameter list somewhere before the `"-jar"` parameter, for example:
If you installed Tomcat via download and unzip from [https://tomcat.apache.org](https://tomcat.apache.org), then you should have a file `<tomcat>/bin/catalina.sh`. Create a new file in the same directory named `<tomcat>/bin/setenv.sh` with the following content:
If the file `<tomcat>/bin/setenv.sh` already exists, then modify that file and add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to `CATALINA_OPTS`.
57
+
If the file `<tomcat>/bin/setenv.sh` already exists, then modify that file and add `-javaagent:path/to/applicationinsights-agent-3.2.4.jar` to `CATALINA_OPTS`.
58
58
59
59
60
60
## Tomcat 8 (Windows)
@@ -64,36 +64,36 @@ If the file `<tomcat>/bin/setenv.sh` already exists, then modify that file and a
64
64
Locate the file `<tomcat>/bin/catalina.bat`. Create a new file in the same directory named `<tomcat>/bin/setenv.bat` with the following content:
65
65
66
66
```
67
-
set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.2.3.jar
67
+
set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.2.4.jar
68
68
```
69
69
70
70
Quotes are not necessary, but if you want to include them, the proper placement is:
71
71
72
72
```
73
-
set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.2.3.jar"
73
+
set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.2.4.jar"
74
74
```
75
75
76
-
If the file `<tomcat>/bin/setenv.bat` already exists, just modify that file and add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to `CATALINA_OPTS`.
76
+
If the file `<tomcat>/bin/setenv.bat` already exists, just modify that file and add `-javaagent:path/to/applicationinsights-agent-3.2.4.jar` to `CATALINA_OPTS`.
77
77
78
78
### Running Tomcat as a Windows service
79
79
80
-
Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to the `Java Options` under the `Java` tab.
80
+
Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.2.4.jar` to the `Java Options` under the `Java` tab.
81
81
82
82
83
83
## JBoss EAP 7
84
84
85
85
### Standalone server
86
86
87
-
Add `-javaagent:path/to/applicationinsights-agent-3.2.3.jar` to the existing `JAVA_OPTS` environment variable in the file `JBOSS_HOME/bin/standalone.conf` (Linux) or `JBOSS_HOME/bin/standalone.conf.bat` (Windows):
87
+
Add `-javaagent:path/to/applicationinsights-agent-3.2.4.jar` to the existing `JAVA_OPTS` environment variable in the file `JBOSS_HOME/bin/standalone.conf` (Linux) or `JBOSS_HOME/bin/standalone.conf.bat` (Windows):
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/java-standalone-config.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,14 @@ You will find more details and additional configuration options below.
36
36
37
37
## Configuration file path
38
38
39
-
By default, Application Insights Java 3.x expects the configuration file to be named `applicationinsights.json`, and to be located in the same directory as `applicationinsights-agent-3.2.3.jar`.
39
+
By default, Application Insights Java 3.x expects the configuration file to be named `applicationinsights.json`, and to be located in the same directory as `applicationinsights-agent-3.2.4.jar`.
40
40
41
41
You can specify your own configuration file path using either
42
42
43
43
*`APPLICATIONINSIGHTS_CONFIGURATION_FILE` environment variable, or
44
44
*`applicationinsights.configuration.file` Java system property
45
45
46
-
If you specify a relative path, it will be resolved relative to the directory where `applicationinsights-agent-3.2.3.jar` is located.
46
+
If you specify a relative path, it will be resolved relative to the directory where `applicationinsights-agent-3.2.4.jar` is located.
47
47
48
48
## Connection string
49
49
@@ -508,7 +508,7 @@ and the console, corresponding to this configuration:
508
508
`level` can be one of `OFF`, `ERROR`, `WARN`, `INFO`, `DEBUG`, or `TRACE`.
509
509
510
510
`path` can be an absolute or relative path. Relative paths are resolved against the directory where
511
-
`applicationinsights-agent-3.2.3.jar` is located.
511
+
`applicationinsights-agent-3.2.4.jar` is located.
512
512
513
513
`maxSizeMb` is the max size of the log file before it rolls over.
0 commit comments