Skip to content

Commit b2e7b45

Browse files
Sarabaduggailey777
authored andcommitted
show custom track for v4 functions
1 parent 75fff9c commit b2e7b45

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

articles/azure-functions/functions-reference-node.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1116,8 +1116,6 @@ In addition to the default `context.log` method, the following methods are avail
11161116
11171117
Azure Functions lets you define the threshold level to be used when tracking and viewing logs. To set the threshold, use the `logging.logLevel` property in the `host.json` file. This property lets you define a default level applied to all functions, or a threshold for each individual function. To learn more, see [How to configure monitoring for Azure Functions](configure-monitoring.md).
11181118
1119-
::: zone pivot="nodejs-model-v3"
1120-
11211119
## Track custom data
11221120
11231121
By default, Azure Functions writes output as traces to Application Insights. For more control, you can instead use the [Application Insights Node.js SDK](https://github.com/microsoft/applicationinsights-node.js) to send custom data to your Application Insights instance.
@@ -1237,8 +1235,6 @@ export default httpTrigger;
12371235
12381236
The `tagOverrides` parameter sets the `operation_Id` to the function's invocation ID. This setting enables you to correlate all of the automatically generated and custom logs for a given function invocation.
12391237
1240-
::: zone-end
1241-
12421238
<a name="http-triggers-and-bindings"></a>
12431239
12441240
## HTTP triggers

0 commit comments

Comments
 (0)