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/essentials/activity-log.md
+13-17Lines changed: 13 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,21 +13,17 @@ ms.reviewer: orens
13
13
14
14
The Azure Monitor Activity Log is a platform log that provides insight into subscription-level events. The Activity Log includes information like when a resource is modified or a virtual machine is started. You can view the Activity Log in the Azure portal or retrieve entries with PowerShell and the Azure CLI. This article provides information on how to view the Activity Log and send it to different destinations.
15
15
16
-
For more functionality, create a diagnostic setting to send the Activity Log to one or more of these locations:
Create a diagnostic setting to send the Activity Log to one or more of these locations:
17
+
-[Log Analytics workspace](#send-to-log-analytics-workspace) for more complex querying and alerting
18
+
-[Azure Event Hubs](#send-to-azure-event-hubs) to forwarding logs outside of Azure.
19
+
-[Azure Storage](#send-to-azure-storage) for cheaper, long-term archiving.
20
20
21
-
Sending the Activity Log to one of these locations has several benefits:
22
-
23
-
- Send to a [Logs Analytics workspace](../logs/data-platform-logs.md) for more complex querying and alerting.
24
-
- Send to Azure Event Hubs to forward outside of Azure.
25
-
- Send to Azure Storage for cheaper, long-term archiving.
26
21
27
22
For details on how to create a diagnostic setting, see [Create diagnostic settings to send platform logs and metrics to different destinations](./diagnostic-settings.md).
28
23
> [!TIP]
24
+
> Send Activity Logs to a Log Analytics workspace for the following benefits:
29
25
> * Sending logs to a Log Analytics workspace is free of charge for the default retention period.
30
-
> *Sending logs to a Log Analytics workspace for [longer retention of up to 12 years](../logs/data-retention-configure.md).
26
+
> *Send logs to a Log Analytics workspace for [longer retention of up to 12 years](../logs/data-retention-configure.md).
31
27
> * Logs exported to a Log Analytics workspace can be [shown in Power BI](/power-bi/transform-model/log-analytics/desktop-log-analytics-overview)
32
28
> *[Insights](./activity-log-insights.md) are provided for Activity Logs exported to Log Analytics.
33
29
@@ -253,12 +249,12 @@ If a log profile already exists, you first must remove the existing log profile,
253
249
```
254
250
| Property | Required | Description |
255
251
| --- | --- | --- |
256
-
| name |Yes |Name of your log profile. |
257
-
| storage-account-id |Yes |Resource ID of the storage account to which activity logs should be saved. |
258
-
| locations |Yes |Space-separated list of regions for which you want to collect activity log events. View a list of all regions for your subscription by using `az account list-locations --query [].name`. |
259
-
| days |Yes |Number of days for which events should be retained, from 1 through 365. A value of zero stores the logs indefinitely (forever). If zero, then the enabled parameter should be set to False. |
260
-
|enabled | Yes |True or False. Used to enable or disable the retention policy. If True, then the `days` parameter must be a value greater than zero.
261
-
| categories |Yes |Space-separated list of event categories that should be collected. Possible values are Write, Delete, and Action. |
252
+
|`name`|Yes |Name of your log profile. |
253
+
|`storage-account-id`|Yes |Resource ID of the storage account to which activity logs should be saved. |
254
+
|`locations`|Yes |Space-separated list of regions for which you want to collect activity log events. View a list of all regions for your subscription by using `az account list-locations --query [].name`. |
255
+
|`days`|Yes |Number of days for which events should be retained, from 1 through 365. A value of zero stores the logs indefinitely (forever). If zero, then the enabled parameter should be set to False. |
256
+
|`enabled` | Yes |True or False. Used to enable or disable the retention policy. If True, then the `days` parameter must be a value greater than zero.
257
+
|`categories`|Yes |Space-separated list of event categories that should be collected. Possible values are Write, Delete, and Action. |
262
258
263
259
264
260
---
@@ -267,7 +263,7 @@ If a log profile already exists, you first must remove the existing log profile,
267
263
268
264
The Export activity logs experience sends the same data as the legacy method used to send the activity log with some changes to the structure of the `AzureActivity` table.
269
265
270
-
The columns in the following table have been deprecated in the updated schema. They still exist in `AzureActivity`, but they have no data. The replacements for these columns aren't new, but they contain the same data as the deprecated column. They're in a different format, so you might need to modify log queries that use them.
266
+
The columns in the following table are deprecated in the updated schema. They still exist in `AzureActivity`, but they have no data. The replacements for these columns aren't new, but they contain the same data as the deprecated column. They're in a different format, so you might need to modify log queries that use them.
271
267
272
268
|Activity log JSON | Log Analytics column name<br/>*(older deprecated)*| New Log Analytics column name | Notes |
0 commit comments