Closed arynaq closed 2 years ago
Try AF tagging perhaps?
https://www.codeproject.com/Tips/5294072/Add-tags-to-Azure-functions-Application-Insights
@RohitRanjanMS Could you help with this question?
thanks @kshyju, I will have a look at it.
Hi @arynaq we don't apply any filter on the log stream. You see everything that is getting logged in AI. You have some ability to apply filters when you go to "Open in Live Metrics" or open it directly from ApplicationInsights.
Hi @arynaq we don't apply any filter on the log stream. You see everything that is getting logged in AI. You have some ability to apply filters when you go to "Open in Live Metrics" or open it directly from ApplicationInsights.
One might think the issue is not having one log stream per one Azure Function.
Hi @arynaq, it's a fair expectation, probably the confusion is because you are viewing it from a specific function app. Streaming is AI capability; we only fetch the logs from AI and show it in on the portal without any filter.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
I couldn't find any related issues here (might be my lacking search-fu) but we are seeing some weird/unexpected behavior in azure function app log streaming (in Function App -> Monitor -> Log stream) in the portal. I suspect the weird behavior is caused by the fact that we have more than one app / function streaming to the same app insights instance, but that I gather to be the whole point, to have centralized logging on the platform.
There are two issues:
Issue A
Issue B
2022-08-31T10:49:33.460Z [info][LogStreamFrameBladeReact][selectedLoggingOption][clicked]
Investigative information
Please provide the following:
022-08-31T10:49:33.460Z
3.12.1.0
hansalgoliasyncprodapp
N/A
2ebb2e1f-a503-4ab5-a59f-e639c95d90ed
Norway East
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
Actual behavior
Known workarounds
Be slower in iterations and wait for actual logs in app insights so traces can be filtered with KQL, not optimal.