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
For dotnet-isolated app, All the warning log statements are written to C:\home\LogFiles\eventlog.xml. The issue can be reproduced by creating a dotnet-isolated app on windows with consumption plan and adding a warning statement like the one below to an httpTrigger function.
We should not be warning logs to eventlog.xml file by default.
usingMicrosoft.AspNetCore.Http;usingMicrosoft.AspNetCore.Mvc;usingMicrosoft.Azure.Functions.Worker;usingMicrosoft.Extensions.Logging;namespaceFunctionApp1{publicclassHttpTrigger1{privatereadonlyILogger<HttpTrigger1>_logger;publicHttpTrigger1(ILogger<HttpTrigger1>logger){_logger=logger;}[Function("HttpTrigger1")]publicIActionResultRun([HttpTrigger(AuthorizationLevel.Function,"get","post")]HttpRequestreq){_logger.LogInformation("C# HTTP trigger function processed a request.");_logger.LogWarning("Warning: C# HTTP trigger function processed a request.");returnnewOkObjectResult("Welcome to Azure Functions!");}}}
For dotnet-isolated app, All the warning log statements are written to
C:\home\LogFiles\eventlog.xml
. The issue can be reproduced by creating a dotnet-isolated app on windows with consumption plan and adding a warning statement like the one below to an httpTrigger function.We should not be warning logs to eventlog.xml file by default.
Sample Host.json
Sample httpTrigger
EventLog.xml
The text was updated successfully, but these errors were encountered: