Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions articles/azure-functions/dotnet-isolated-process-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -807,6 +807,13 @@ public class MyFunction {
}
```

> [!NOTE]
> Loggers obtained through dependency injection are associated with a log category set to the fully qualified name of the class.
> This usually consists in a category name with one or more `.` (period) characters.
> When hosting your function app on Linux App Service plans, please be aware of
> [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
> log levels for those categories using environment variables.

The logger can also be obtained 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. To learn more about categories, see the [monitoring article](functions-monitoring.md#log-levels-and-categories).

Use the methods of [`ILogger<T>`][ILogger&lt;T&gt;] and [`ILogger`][ILogger] to write various log levels, such as `LogWarning` or `LogError`. To learn more about log levels, see the [monitoring article](functions-monitoring.md#log-levels-and-categories). You can customize the log levels for components added to your code by registering filters:
Expand Down