Skip to content

Commit 7c10fb4

Browse files
committed
Updating note
1 parent 870e1f1 commit 7c10fb4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-monitor/logs/functions.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,9 @@ ms.date: 06/22/2022
1313
A function is a log query in Azure Monitor that can be used in other log queries as though it's a command. You can use functions to provide solutions to different customers and also reuse query logic in your own environment. This article describes how to use functions and how to create your own.
1414

1515
> [!NOTE]
16-
> Functions are only available from Log Analytics workspaces. If you’re using an existing classic Application Insights resource, you must [migrate it to a workspace-based resource](../app/convert-classic-resource) to work with functions. Choosing to migrate will give you access to the same logs but you need to [validate that a query’s fields align with the new schema fields](../app/convert-classic-resource#table-schemas). After migration, you can use a Log Analytics workspace to query the AzureActivity table, which isn't available for classic resources.
16+
> Functions are only available in Log Analytics workspaces. If you’re using an existing classic Application Insights resource, you must [migrate it to a workspace-based resource](../app/convert-classic-resource) to work with functions.
17+
>
18+
> Choosing to migrate gives you access to logs with the same general structure as classic resources although the [table and column names are different](../app/convert-classic-resource.md#workspace-based-resource-changes). Migrating also allows you to send activity logs to a Log Analytics workspace in a table called AzureActivity. The AzureActivity table isn't available in classic resources.
1719
1820
## Types of functions
1921
There are two types of functions in Azure Monitor:

0 commit comments

Comments
 (0)