Azure / Azure/azure-functions-host

Application logs not working when function's project is on .NET Core 2.2 (also before latest release)

Open
#3,946 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

#### Investigative information

Please provide the following:

- Timestamp:
- Function App version (1.0 or 2.0): 2.0
- Function App name:
- Function name(s) (as appropriate):
- Invocation ID:
- Region:

#### Repro steps

Provide the steps required to reproduce the problem:
1. Update function's project in VS to .NET Core 2.2
2. Get an error when passing ILogger to the trigger method
3. (Optionally) Implement your own logger (e.g. Serilog) and observe that nothing is being logged in the function's application log (console in the Azure Portal and log files in the Azure storage).

#### Expected behavior

Logging should be working as with .NET Core 2.1

#### Actual behavior

Logging is broken.

#### Known workarounds

Provide a description of any known workarounds.

None that provide logging to the function's application log.

#### Related information

Provide any related information

* Programming language used
* Links to source
* Bindings used

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with a Function App on .NET Core 2.2 using the listed trigger and ILogger, then compare behavior with .NET Core 2.1. Check both the Azure Portal console and Azure Storage log files; done means built-in and custom logging appear in the function's application log without the reported ILogger error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
backend, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.