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/platform/activity-log-collect.md
+10-22Lines changed: 10 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,10 @@ Collecting the Activity Log in a Log Analytics workspace provides the following
16
16
17
17
- No data ingestion or data retention charge for Activity log data stored in a Log Analytics workspace.
18
18
- Correlate Activity log data with other monitoring data collected by Azure Monitor.
19
-
- Use [log queries](../log-query/log-query-overview.md) to perform complex analysis and gain deep insights on Activity Log entries.
19
+
- Use log queries to perform complex analysis and gain deep insights on Activity Log entries.
20
+
- Use log alerts with Activity entries allowing for more complex alerting logic.
20
21
- Store Activity log entries for longer than 90 days.
21
-
- Consolidate log entries from multiple Azure subscriptions into one location for analysis together.
22
+
- Consolidate log entries from multiple Azure subscriptions and tenants into one location for analysis together.
22
23
23
24
24
25
@@ -31,7 +32,7 @@ To create a diagnostic setting for the Activity log, select **Diagnostic setting
31
32
32
33
33
34
> [!NOTE]
34
-
> Currently, you can only create a subscription level diagnostic setting using the Azure portal. To use other methods such as PowerShell or CLI, you can create a Resource Manager template.
35
+
> Currently, you can only create a subscription level diagnostic setting using the Azure portal and a Resource Manager template.
35
36
36
37
37
38
## Legacy settings
@@ -44,6 +45,7 @@ While diagnostic settings are the preferred method to send the Activity log to d
44
45
- Faster latency for log ingestion. The previous method has about 15 minutes latency while diagnostic settings adds only about 1 minute.
45
46
46
47
48
+
47
49
### Log profiles
48
50
Log profiles are the legacy method for sending the Activity log to Azure storage or event hubs. Use the following procedure to continue working with a log profile or to disable it in preparation for migrating to a diagnostic setting.
49
51
@@ -89,32 +91,18 @@ The columns in the following table have been deprecated in the updated schema. T
89
91
| OperationName | OperationNameValue |
90
92
| ResourceProvider | ResourceProviderValue |
91
93
94
+
> [!IMPORTANT]
95
+
> In some cases, the values in these columns may be in all uppercase. If you have a query that includes these columns, you should use the [=~ operator](https://docs.microsoft.com/azure/kusto/query/datatypes-string-operators) to do a case insensitive comparison.
96
+
92
97
The following column have been added to *AzureActivity* in the updated schema:
93
98
94
99
- Authorization_d
95
100
- Claims_d
96
101
- Properties_d
97
102
98
-
> [!IMPORTANT]
99
-
> In some cases, the values in these columns may be in all uppercase. If you have a query that includes these columns, you should use the [=~ operator](https://docs.microsoft.com/azure/kusto/query/datatypes-string-operators) to do a case insensitive comparison.
100
-
101
-
102
-
### Query samples
103
-
Following are sample queries retrieving Activity log data using log queries.
104
-
105
-
### List all records for starting virtual machines
106
-
107
-
```Kusto
108
-
AzureActivity
109
-
| where TimeGenerated > ago(7d)
110
-
| where ResourceProviderValue == "MICROSOFT.COMPUTE"
111
-
| where OperationNameValue == "MICROSOFT.COMPUTE/VIRTUALMACHINES/START/ACTION"
112
-
```
113
-
114
-
115
103
116
104
## Activity Logs Analytics monitoring solution
117
-
The Azure Log Analytics monitoring solution is currently being deprecated and will soon be replaced by a workbook using the updated schema in the Log Analytics workspace. You can still use the solution if you already have it enabled, but it can only be used if you're collecting the Activity log using legacy settings.
105
+
The Azure Log Analytics monitoring solution will be deprecated soon and replaced by a workbook using the updated schema in the Log Analytics workspace. You can still use the solution if you already have it enabled, but it can only be used if you're collecting the Activity log using legacy settings.
118
106
119
107
120
108
@@ -130,7 +118,7 @@ Click the **Azure Activity Logs** tile to open the **Azure Activity Logs** view.
130
118
131
119
132
120
### Enable the solution for new subscriptions
133
-
You can no longer add a new subscription to the Activity Logs Analytics solution using the Azure portal, but you can add a new subscription using a resource manager template.
121
+
You soon no longer be able to add a new subscription to the Activity Logs Analytics solution using the Azure portal, but you can add a new subscription using a resource manager template.
134
122
135
123
1. Copy the following json into a file called *ActivityLogTemplate*.json.
0 commit comments