Azure / Azure-Functions

1.11k stars 196 forks source link

In Azure portal, Azure Function invocation logs do not show up #2114

Open anitaandonoska3 opened 2 years ago

anitaandonoska3 commented 2 years ago

Hi, when checking the invocation logs for an Azure function, for some of the invocations I can see the logs:

image

But for others the log is empty: image

Why is this happening? Is there another way to see the logs per function invocation? Thanks!

Ved2806 commented 2 years ago

Hi @anitaandonoska3, Thank you for your feedback! There are three ways to check the logs for the function invocation. Please find them on the link below. https://www.markheath.net/post/three-ways-view-error-logs-azure-functions Kindly let us know if that helps.

anitaandonoska3 commented 2 years ago

@Ved2806 thanks for the reply! But do you know what could be the reason why the logs do not show up? Thanks!

Ved2806 commented 2 years ago

Hi @anitaandonoska3 This is just the behavior of logs that you won't see every single log in application insights.

anitaandonoska3 commented 2 years ago

Hi, it looks like a bug, since there is a window for the log to show up but is empty.

Ved2806 commented 2 years ago

Thank you for the feedback! We will check for the possibilities internally and update you with the findings.

Sudhar287 commented 1 year ago

I have a weird case where some of my successful azure function invocations are logged but most others arent! From the discussion above, @Ved2806 do you mean that not logs will be stored? May I please have the docs that state this behavior?

dashightech commented 1 year ago

Neither can I see invocations of my functions. They do run but I cant see invocations.

Here are my functions: image

When I click Invocations and more I get a blank white page: image

I get an error in Chrome DevTools: image

mikejwhat commented 1 year ago

Is anything happening with this? It's really frustrating when this doesn't work because it's a useful tool when it does.

TechnicallyJoe commented 6 months ago

same is happening here. except i can't see it for any of the logs. Seeing the same error in devtools though