Skip to content

Commit 2f52be8

Browse files
committed
fixes
1 parent d317769 commit 2f52be8

File tree

1 file changed

+13
-17
lines changed

1 file changed

+13
-17
lines changed

articles/azure-monitor/essentials/activity-log.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,17 @@ ms.reviewer: orens
1313

1414
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.
1515

16-
For more functionality, 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)
18-
- [Azure Event Hubs](#send-to-azure-event-hubs)
19-
- [Azure Storage](#send-to-azure-storage)
16+
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.
2020

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.
2621

2722
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).
2823
> [!TIP]
24+
> Send Activity Logs to a Log Analytics workspace for the following benefits:
2925
> * 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).
3127
> * Logs exported to a Log Analytics workspace can be [shown in Power BI](/power-bi/transform-model/log-analytics/desktop-log-analytics-overview)
3228
> * [Insights](./activity-log-insights.md) are provided for Activity Logs exported to Log Analytics.
3329
@@ -253,12 +249,12 @@ If a log profile already exists, you first must remove the existing log profile,
253249
```
254250
| Property | Required | Description |
255251
| --- | --- | --- |
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. |
262258

263259

264260
---
@@ -267,7 +263,7 @@ If a log profile already exists, you first must remove the existing log profile,
267263

268264
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.
269265

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.
271267

272268
|Activity log JSON | Log Analytics column name<br/>*(older deprecated)* | New Log Analytics column name | Notes |
273269
|:---------|:---------|:---------|:---------|

0 commit comments

Comments
 (0)