Skip to content

Commit 8ac9a98

Browse files
committed
fixes
1 parent e55c848 commit 8ac9a98

File tree

1 file changed

+10
-22
lines changed

1 file changed

+10
-22
lines changed

articles/azure-monitor/platform/activity-log-collect.md

Lines changed: 10 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,10 @@ Collecting the Activity Log in a Log Analytics workspace provides the following
1616

1717
- No data ingestion or data retention charge for Activity log data stored in a Log Analytics workspace.
1818
- 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.
2021
- 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.
2223

2324

2425

@@ -31,7 +32,7 @@ To create a diagnostic setting for the Activity log, select **Diagnostic setting
3132

3233

3334
> [!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.
3536
3637

3738
## Legacy settings
@@ -44,6 +45,7 @@ While diagnostic settings are the preferred method to send the Activity log to d
4445
- Faster latency for log ingestion. The previous method has about 15 minutes latency while diagnostic settings adds only about 1 minute.
4546

4647

48+
4749
### Log profiles
4850
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.
4951

@@ -89,32 +91,18 @@ The columns in the following table have been deprecated in the updated schema. T
8991
| OperationName | OperationNameValue |
9092
| ResourceProvider | ResourceProviderValue |
9193

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+
9297
The following column have been added to *AzureActivity* in the updated schema:
9398

9499
- Authorization_d
95100
- Claims_d
96101
- Properties_d
97102

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-
115103

116104
## 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.
118106

119107

120108

@@ -130,7 +118,7 @@ Click the **Azure Activity Logs** tile to open the **Azure Activity Logs** view.
130118

131119

132120
### 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.
134122

135123
1. Copy the following json into a file called *ActivityLogTemplate*.json.
136124

0 commit comments

Comments
 (0)