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
Note that completion will incur a small cost of a few USD cents or less in your Azure account.
17
+
Completion of this quickstart incurs a small cost of a few USD cents or less in your Azure account.
18
18
19
-
There is also a [Visual Studio Code-based version](create-first-function-vs-code-node.md) of this article.
19
+
There's also a [Visual Studio Code-based version](create-first-function-vs-code-node.md) of this article.
20
20
21
21
## Configure your local environment
22
22
23
-
Before you begin, you must have the following:
23
+
Before you begin, you must have the following prerequisites:
24
24
25
25
+ An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
26
26
@@ -48,7 +48,7 @@ Before you begin, you must have the following:
48
48
49
49
### Prerequisite check
50
50
51
-
Verify your prerequisites, which depend on whether you are using Azure CLI or Azure PowerShell for creating Azure resources:
51
+
Verify your prerequisites, which depend on whether you're using Azure CLI or Azure PowerShell for creating Azure resources:
52
52
53
53
# [Azure CLI](#tab/azure-cli)
54
54
@@ -137,7 +137,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
137
137
```console
138
138
func init LocalFunctionProj --model V4
139
139
```
140
-
You are then prompted to choose a worker runtime and a language - choose Node for the first and JavaScript for the second.
140
+
You're then prompted to choose a worker runtime and a language - choose Node for the first and JavaScript for the second.
141
141
142
142
2. Navigate into the project folder:
143
143
@@ -153,7 +153,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
153
153
func new
154
154
```
155
155
156
-
Choose the template for "HTTP trigger". You can keep the default name (*httpTrigger*) or give it a new name (*HttpExample*). Your function name must be unique, or you'll be asked to confirm if your intention is to replace an existing function.
156
+
Choose the template for "HTTP trigger". You can keep the default name (*httpTrigger*) or give it a new name (*HttpExample*). Your function name must be unique, or you're asked to confirm if your intention is to replace an existing function.
157
157
158
158
You can find the function you added in the *src/functions* directory.
159
159
@@ -187,21 +187,21 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
The [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command creates the function app in Azure. It is recommended that you use the latest version of Node.js, which is currently 18. You can specify the version by setting `--runtime-version` to `18`.
190
+
The [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command creates the function app in Azure. It's recommended that you use the latest version of Node.js, which is currently 18. You can specify the version by setting `--runtime-version` to `18`.
The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. It is recommended that you use the latest version of Node.js, which is currently 18. You can specify the version by setting `--runtime-version` to `18`.
198
+
The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. It's recommended that you use the latest version of Node.js, which is currently 18. You can specify the version by setting `--runtime-version` to `18`.
199
199
200
200
---
201
201
202
202
In the previous example, replace `<STORAGE_NAME>` with the name of the account you used in the previous step, and replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default DNS domain for the function app.
203
203
204
-
This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also provisions an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
204
+
This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also creates an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
Note that completion will incur a small cost of a few USD cents or less in your Azure account.
17
+
Completion of this quickstart incurs a small cost of a few USD cents or less in your Azure account.
18
18
19
19
There's also a [Visual Studio Code-based version](create-first-function-vs-code-typescript.md) of this article.
20
20
21
21
## Configure your local environment
22
22
23
-
Before you begin, you must have the following:
23
+
Before you begin, you must have the following prerequisites:
24
24
25
25
+ An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
26
26
@@ -153,7 +153,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
153
153
func new
154
154
```
155
155
156
-
Choose the template for "HTTP trigger". You can keep the default name (*httpTrigger*) or give it a new name (*HttpExample*). Your function name must be unique, or you'll be asked to confirm if your intention is to replace an existing function.
156
+
Choose the template for "HTTP trigger". You can keep the default name (*httpTrigger*) or give it a new name (*HttpExample*). Your function name must be unique, or you're asked to confirm if your intention is to replace an existing function.
157
157
158
158
You can find the function you added in the *src/functions* directory.
159
159
@@ -191,20 +191,20 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
191
191
```
192
192
::: zone-end
193
193
194
-
Toward the end of the output, the following should appear:
194
+
Toward the end of the output, the following logs should appear:
195
195
196
196

197
197
198
198
>[!NOTE]
199
-
> If HttpExample doesn't appear as shown below, you likely started the host from outside the root folder of the project. In that case, use **Ctrl**+**C** to stop the host, navigate to the project's root folder, and run the previous command again.
199
+
> If HttpExample doesn't appear as shown in the logs, you likely started the host from outside the root folder of the project. In that case, use <kbd>Ctrl</kbd>+<kbd>c</kbd> to stop the host, navigate to the project's root folder, and run the previous command again.
200
200
201
201
1. Copy the URL of your `HttpExample` function from this output to a browser and append the query string `?name=<your-name>`, making the full URL like `http://localhost:7071/api/HttpExample?name=Functions`. The browser should display a message like `Hello Functions`:
202
202
203
203

204
204
205
205
The terminal in which you started your project also shows log output as you make requests.
206
206
207
-
1. When you're ready, use **Ctrl**+**C** and choose `y` to stop the functions host.
207
+
1. When you're ready, use <kbd>Ctrl</kbd>+<kbd>c</kbd> and choose <kbd>y</kbd> to stop the functions host.
@@ -230,7 +230,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
230
230
231
231
In the previous example, replace `<STORAGE_NAME>` with the name of the account you used in the previous step, and replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default DNS domain for the function app.
232
232
233
-
This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also provisions an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
233
+
This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also creates an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
234
234
235
235
::: zone pivot="nodejs-model-v4"
236
236
## Update app settings
@@ -264,7 +264,7 @@ Before you use Core Tools to deploy your project to Azure, you create a producti
264
264
npm run build
265
265
```
266
266
267
-
1. With the necessary resources in place, you're now ready to deploy your local functions project to the function app in Azure by using the [func azure functionapp publish](functions-run-local.md#project-file-deployment) command. In the following example, replace `<APP_NAME>` with the name of your app.
267
+
1. With the necessary resources in place, you're now ready to deploy your local functions project to the function app in Azure by using the [publish](functions-run-local.md#project-file-deployment) command. In the following example, replace `<APP_NAME>` with the name of your app.
Note that completion will incur a small cost of a few USD cents or less in your Azure account.
21
+
Completion of this quickstart incurs a small cost of a few USD cents or less in your Azure account.
22
22
23
23
There's also a [CLI-based version](create-first-function-cli-node.md) of this article.
24
24
@@ -35,7 +35,7 @@ Before you get started, make sure you have the following requirements in place:
35
35
36
36
## <aname="create-an-azure-functions-project"></a>Create your local project
37
37
38
-
In this section, you use Visual Studio Code to create a local Azure Functions project in JavaScript. Later in this article, you'll publish your function code to Azure.
38
+
In this section, you use Visual Studio Code to create a local Azure Functions project in JavaScript. Later in this article, you publish your function code to Azure.
39
39
40
40
1. Choose the Azure icon in the Activity bar. Then in the **Workspace (local)** area, select the **+** button, choose **Create Function** in the dropdown. When prompted, choose **Create new project**.
41
41
@@ -150,7 +150,7 @@ To enable your V4 programming model app to run in Azure, you need to add a new a
150
150
```
151
151
1. [Rerun the function](#run-the-function-locally) app locally.
152
152
153
-
1. In the prompt **Enter request body** change the request message body to { "name":"Tom","sport":"basketball" }. PressEntertosendthisrequestmessagetoyourfunction.
153
+
1. In the prompt **Enter request body**, change the request message body to { "name":"Tom","sport":"basketball" }. PressEntertosendthisrequestmessagetoyourfunction.
154
154
155
155
1. View the response in the notification:
156
156
@@ -168,7 +168,7 @@ To enable your V4 programming model app to run in Azure, you need to add a new a
168
168
169
169
## Troubleshooting
170
170
171
-
Use the table below to resolve the most common issues encountered when using this quickstart.
171
+
Use the following table to resolve the most common issues encountered when using this quickstart.
Note that completion will incur a small cost of a few USD cents or less in your Azure account.
17
+
Completion of this quickstart incurs a small cost of a few USD cents or less in your Azure account.
18
18
19
19
There's also a [CLI-based version](create-first-function-cli-typescript.md) of this article.
20
20
@@ -46,7 +46,7 @@ Before you get started, make sure you have the following requirements in place:
46
46
47
47
## <aname="create-an-azure-functions-project"></a>Create your local project
48
48
49
-
In this section, you use Visual Studio Code to create a local Azure Functions project in TypeScript. Later in this article, you'll publish your function code to Azure.
49
+
In this section, you use Visual Studio Code to create a local Azure Functions project in TypeScript. Later in this article, you publish your function code to Azure.
50
50
51
51
1. Choose the Azure icon in the Activity bar. Then in the **Workspace (local)** area, select the **+** button, choose **Create Function** in the dropdown. When prompted, choose **Create new project**.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-monitoring.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ By assigning logged items to a category, you have more control over telemetry ge
85
85
86
86
### Custom telemetry data
87
87
88
-
In [C#](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions), [JavaScript](functions-reference-node.md#log-custom-telemetry), and [Python](functions-reference-python.md#log-custom-telemetry), you can use an Application Insights SDK to write custom telemetry data.
88
+
In [C#](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions), [JavaScript](functions-reference-node.md#track-custom-data), and [Python](functions-reference-python.md#log-custom-telemetry), you can use an Application Insights SDK to write custom telemetry data.
89
89
90
90
### Dependencies
91
91
@@ -107,7 +107,7 @@ Dependencies are written at the `Information` level. If you filter at `Warning`
107
107
In addition to automatic dependency data collection, you can also use one of the language-specific Application Insights SDKs to write custom dependency information to the logs. For an example how to write custom dependencies, see one of the following language-specific examples:
108
108
109
109
+[Log custom telemetry in C# functions](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions)
110
-
+[Log custom telemetry in JavaScript functions](functions-reference-node.md#log-custom-telemetry)
110
+
+[Log custom telemetry in JavaScript functions](functions-reference-node.md#track-custom-data)
111
111
+[Log custom telemetry in Python functions](functions-reference-python.md#log-custom-telemetry)
0 commit comments