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
title: Automate Azure Application Insights processes by using Logic Apps
2
+
title: Automate Application Insights processes by using Logic Apps
3
3
description: Learn how you can quickly automate repeatable processes by adding the Application Insights connector to your logic app.
4
4
ms.topic: conceptual
5
5
ms.date: 07/31/2022
@@ -10,63 +10,64 @@ ms.reviewer: yossi-y
10
10
11
11
# Automate Application Insights processes by using Logic Apps
12
12
13
-
Do you find yourself repeatedly running the same queries on your telemetry data to check whether your service is functioning properly? Are you looking to automate these queries for finding trends and anomalies and then build your own workflows around them? The Azure Application Insights connector for Logic Apps is the right tool for this purpose.
13
+
Do you find yourself repeatedly running the same queries on your telemetry data to check whether your service is functioning properly? Are you looking to automate these queries for finding trends and anomalies and then build your own workflows around them? The Application Insights connector for Azure Logic Apps is the right tool for this purpose.
14
14
15
15
> [!NOTE]
16
-
> The Azure Application Insights connector has been replaced by the [Azure Monitor connector](../logs/logicapp-flow-connector.md), which is integrated with Azure Active Directory instead of requiring an API key and also allows you to retrieve data from a Log Analytics workspace.
16
+
> The Application Insights connector has been replaced by the [Azure Monitor connector](../logs/logicapp-flow-connector.md). It's integrated with Azure Active Directory instead of requiring an API key. You can also use it to retrieve data from a Log Analytics workspace.
17
17
18
-
With this integration, you can automate numerous processes without writing a single line of code. You can create a logic app with the Application Insights connector to quickly automate any Application Insights process.
18
+
With this integration, you can automate numerous processes without writing a single line of code. You can create a logic app with the Application Insights connector to quickly automate any Application Insights process.
19
19
20
-
You can also add other actions. The Logic Apps feature of Azure App Service makes hundreds of actions available. For example, by using a logic app, you can automatically send an email notification or create a bug in Azure DevOps. You can also use one of the many available [templates](../../logic-apps/logic-apps-create-logic-apps-from-templates.md) to help speed up the process of creating your logic app.
20
+
You can also add other actions. The Logic Apps feature of Azure App Service makes hundreds of actions available. For example, by using a logic app, you can automatically send an email notification or create a bug in Azure DevOps. You can also use one of the many available [templates](../../logic-apps/logic-apps-create-logic-apps-from-templates.md) to help speed up the process of creating your logic app.
21
21
22
22
## Create a logic app for Application Insights
23
23
24
-
In this tutorial, you learn how to create a logic app that uses the Analytics autocluster algorithm to group attributes in the data for a web application. The flow automatically sends the results by email, just one example of how you can use Application Insights Analytics and Logic Apps together.
24
+
In this tutorial, you learn how to create a logic app that uses the Analytics autocluster algorithm to group attributes in the data for a web application. The flow automatically sends the results by email. This example shows how you can use Application Insights Analytics and Logic Apps together.
25
25
26
-
### Step 1: Create a logic app
26
+
### Create a logic app
27
27
1. Sign in to the [Azure portal](https://portal.azure.com).
47
50
48
-
51
+
### Connect to an Application Insights resource
49
52
50
-
### Step 4: Connect to an Application Insights resource
53
+
For this step, you need an application ID and an API key for your resource.
51
54
52
-
To complete this step, you need an application ID and an API key for your resource:
55
+
1. Select **API Access** > **Create API key**.
53
56
54
-
1. Select **API access** > **Create API key**:
57
+
55
58
56
-
57
-
58
59
59
60
60
61
1. Provide a name for your connection, the application ID, and the API key.
61
62
62
63
63
64
64
-
### Step 5: Specify the Analytics query and chart type
65
-
In the following example, the query selects the failed requests within the last day and correlates them with exceptions that occurred as part of the operation. Analytics correlates the failed requests, based on the operation_Id identifier. The query then segments the results by using the autocluster algorithm.
65
+
### Specify the Analytics query and chart type
66
+
In the following example, the query selects the failed requests within the last day and correlates them with exceptions that occurred as part of the operation. Analytics correlates the failed requests based on the `operation_Id` identifier. The query then segments the results by using the autocluster algorithm.
66
67
67
-
When you create your own queries, verify that they're working properly in Analytics before you add it to your flow.
68
+
When you create your own queries, verify that they're working properly in Analytics before you add them to your flow.
68
69
69
-
1. In the **Query** box, add the following Analytics query:
70
+
1. In the **Query** box, add the following Log Analytics query:
70
71
71
72
```
72
73
requests
@@ -83,59 +84,51 @@ When you create your own queries, verify that they're working properly in Analyt
83
84
84
85
85
86
86
-
### Step 6: Configure the logic app to send email
87
+
### Configure the logic app to send email
87
88
88
89
1. Select **New step**.
89
90
90
-
1. In the search box, type **Office 365 Outlook**.
91
+
1. In the search box, enter **Office 365 Outlook**.
91
92
92
-
1. Select **Office 365 Outlook - Send an email**.
93
+
1. Select **Send an email - Office 365 Outlook**.
93
94
94
95
95
96
96
97
1. In the **Send an email** window:
97
98
98
-
a. Type the email address of the recipient.
99
-
100
-
b. Type a subject for the email.
101
-
102
-
c. Select anywhere in the **Body** box and then, on the dynamic content menu that opens at the right, select **Body**.
103
-
104
-
d. Select the **Add new parameter** dropdown and select Attachments and Is HTML.
99
+
1. Enter the email address of the recipient.
100
+
1. Enter a subject for the email.
101
+
1. Select anywhere in the **Body** box. On the **Dynamic content** menu that opens at the right, select **Body**.
102
+
1. Select the **Add new parameter** dropdown list and select **Attachments** and **Is HTML**.
105
103
106
104
107
105
108
-
109
-
110
-
1. On the dynamic content menu:
106
+
111
107
112
-
a. Select **Attachment Name**.
108
+
1. On the **Dynamic content** menu:
113
109
114
-
b. Select **Attachment Content**.
115
-
116
-
c. In the **Is HTML** box, select **Yes**.
110
+
1. Select **Attachment Name**.
111
+
1. Select **Attachment Content**.
112
+
1. In the **Is HTML** box, select **Yes**.
117
113
118
-
114
+
119
115
120
-
### Step 7: Save and test your logic app
116
+
### Save and test your logic app
121
117
122
118
1. Select **Save** to save your changes.
123
119
124
120
You can wait for the trigger to run the logic app, or you can run the logic app immediately by selecting **Run**.
125
-
126
-
127
-
128
-
When your logic app runs, the recipients you specified in the email list will receive an email that looks like this:
129
-
130
-
121
+
122
+
123
+
124
+
When your logic app runs, the recipients you specified in the email list will receive an email that looks like this example:
125
+
126
+
131
127
132
128
> [!NOTE]
133
-
> The log app generates an email with a JPG file that depicts the query result set. If your query doesn't return results, the logic app won't create a JPG file.
134
-
129
+
> The log app generates an email with a JPG file that depicts the query result set. If your query doesn't return results, the logic app won't create a JPG file.
130
+
135
131
## Next steps
136
132
137
133
- Learn more about creating [Analytics queries](../logs/get-started-queries.md).
138
134
- Learn more about [Logic Apps](../../logic-apps/logic-apps-overview.md).
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/java-standalone-arguments.md
+34-36Lines changed: 34 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,59 +1,57 @@
1
1
---
2
-
title: Adding the JVM arg - Azure Monitor Application Insights for Java
3
-
description: How to add the JVM arg that enables Azure Monitor Application Insights for Java
2
+
title: Add the JVM arg - Azure Monitor Application Insights for Java
3
+
description: Learn how to add the JVM arg that enables Azure Monitor Application Insights for Java.
4
4
ms.topic: conceptual
5
5
ms.date: 12/14/2022
6
6
ms.devlang: java
7
7
ms.custom: devx-track-java
8
8
ms.reviewer: mmcc
9
9
---
10
10
11
-
# Tips for updating your JVM args - Azure Monitor Application Insights for Java
11
+
# Tips for updating your JVM args: Azure Monitor Application Insights for Java
12
12
13
13
## Azure App Services
14
14
15
-
See [Application Monitoring for Azure App Service and Java](./azure-web-apps-java.md).
15
+
For more information, see [Application monitoring for Azure App Service and Java](./azure-web-apps-java.md).
16
16
17
17
## Azure Functions
18
18
19
-
See[Monitoring Azure Functions with Azure Monitor Application Insights](./monitor-functions.md#distributed-tracing-for-java-applications-public-preview).
19
+
For more information, see[Monitoring Azure Functions with Azure Monitor Application Insights](./monitor-functions.md#distributed-tracing-for-java-applications-public-preview).
20
20
21
21
## Spring Boot
22
22
23
-
Read the Spring Boot documentation [here](../app/java-in-process-agent.md).
23
+
Read the Spring Boot documentation [on this website](../app/java-in-process-agent.md).
24
24
25
25
## Third-party container images
26
26
27
-
If you are using a third-party container image which you cannot modify, mount the Application Insights Java agent jar
28
-
into the container from outside, and set the environment variable for the container
27
+
If you're using a third-party container image that you can't modify, mount the Application Insights Java agent jar into the container from outside. Set the environment variable for the container
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:
42
+
If you installed Tomcat via download and unzip from [https://tomcat.apache.org](https://tomcat.apache.org), 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.4.7.jar` to `CATALINA_OPTS`.
50
-
48
+
If the file `<tomcat>/bin/setenv.sh` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to `CATALINA_OPTS`.
51
49
52
50
## Tomcat 8 (Windows)
53
51
54
-
### Running Tomcat from the command line
52
+
### Run Tomcat from the command line
55
53
56
-
Locate the file `<tomcat>/bin/catalina.bat`. Create a new file in the same directory named `<tomcat>/bin/setenv.bat` with the following content:
54
+
Locate the file `<tomcat>/bin/catalina.bat`. Create a new file in the same directory named `<tomcat>/bin/setenv.bat` with the following content:
57
55
58
56
```
59
57
set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.7.jar
@@ -65,12 +63,11 @@ Quotes aren't necessary, but if you want to include them, the proper placement i
65
63
set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.7.jar"
66
64
```
67
65
68
-
If the file `<tomcat>/bin/setenv.bat` already exists, just modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to `CATALINA_OPTS`.
69
-
70
-
### Running Tomcat as a Windows service
66
+
If the file `<tomcat>/bin/setenv.bat` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to `CATALINA_OPTS`.
71
67
72
-
Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the `Java Options` under the `Java` tab.
68
+
### Run Tomcat as a Windows service
73
69
70
+
Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the `Java Options` under the `Java` tab.
74
71
75
72
## JBoss EAP 7
76
73
@@ -126,19 +123,17 @@ If you're running multiple managed servers on a single host, you'll need to add
126
123
...
127
124
```
128
125
129
-
The specified `applicationinsights.agent.id` value must be unique. It's used to create a subdirectory under the application insights directory, as each JVM process needs its own local application insights config and local application insights log file. Also, if reporting to the central collector, the `applicationinsights.properties` file is shared by the multiple managed servers, and so the specified `applicationinsights.agent.id` is needed to override the `agent.id` setting in that shared file. `applicationinsights.agent.rollup.id` can be similarly specified in the server's `system-properties` if you need to override the `agent.rollup.id` setting per managed server.
130
-
126
+
The specified `applicationinsights.agent.id` value must be unique. It's used to create a subdirectory under the Application Insights directory. Each JVM process needs its own local Application Insights config and local Application Insights log file. Also, if reporting to the central collector, the `applicationinsights.properties` file is shared by the multiple managed servers, so the specified `applicationinsights.agent.id` is needed to override the `agent.id` setting in that shared file. The `applicationinsights.agent.rollup.id` can be similarly specified in the server's `system-properties` if you need to override the `agent.rollup.id` setting per managed server.
0 commit comments