Skip to content

Commit 4a2e9f4

Browse files
springcompggailey777
authored andcommitted
Update dotnet-isolated-process-guide.md
Fixed locale-specific link ; use absolute link to /dotnet instead.
1 parent c298cbb commit 4a2e9f4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/azure-functions/dotnet-isolated-process-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -832,7 +832,7 @@ public class MyFunction {
832832
> Loggers obtained through dependency injection are associated with a log category set to the fully qualified name of the class.
833833
> This usually consists in a category name with one or more `.` (period) characters.
834834
> When hosting your function app on Linux App Service plans, please be aware of
835-
> [limitations with category names that contain a dot](https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=bash#set-log-level-by-command-line-environment-variables-and-other-configuration). You will not be able to override
835+
> [limitations with category names that contain a dot](/dotnet/core/extensions/logging?tabs=bash#set-log-level-by-command-line-environment-variables-and-other-configuration). You will not be able to override
836836
> log levels for those categories using environment variables.
837837

838838
You can also get the logger from a [FunctionContext] object passed to your function. Call the [GetLogger<T>] or [GetLogger] method, passing a string value that is the name for the category in which the logs are written. The category is usually the name of the specific function from which the logs are written. For more information about categories, see the [monitoring article](functions-monitoring.md#log-levels-and-categories).

0 commit comments

Comments
 (0)