Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log messages are displayed twice #775

Closed
paulbatum opened this issue Oct 2, 2018 · 2 comments
Closed

Log messages are displayed twice #775

paulbatum opened this issue Oct 2, 2018 · 2 comments

Comments

@paulbatum
Copy link
Member

Make a new V2 function app in VS, pick http trigger, run the app and trigger the function. You'll get the following output:

info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
      Request starting HTTP/1.1 GET http://localhost:7071/api/Function1
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[1]
      Authorization was successful.
[10/2/2018 9:56:48 PM] Executing 'Function1' (Reason='This function was programmatically called via the host APIs.', Id=289659b2-d03a-4411-b397-e7dd89a23c25)
[10/2/2018 9:56:48 PM] C# HTTP trigger function processed a request.
C# HTTP trigger function processed a request.
[10/2/2018 9:56:48 PM] Executed 'Function1' (Succeeded, Id=289659b2-d03a-4411-b397-e7dd89a23c25)
info: Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor[1]
      Executing ObjectResult, writing value of type 'System.String'.
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
      Request finished in 4363.8027ms 400 text/plain; charset=utf-8

Note that the message C# HTTP trigger function processed a request appears twice, once with a timestamp and once without.

@brettsam
Copy link
Member

brettsam commented Oct 2, 2018

Same as Azure/azure-functions-host#3432

@brettsam
Copy link
Member

brettsam commented Oct 2, 2018

Closing this as a duplicate of the issue linked above -- will be tracking the fix there.

@brettsam brettsam closed this as completed Oct 2, 2018
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants