Line number and path or file name missing when logs maintain in azure applicationinsights for blazorWASM application

Question

Line number and path or file name missing when logs maintain in azure applicationinsights for blazorWASM application

ramesh P 0

I had develop blazorWASM application logs using these links. I had used .NET core 6.0.I had use ILoggers<Type> logger

https://stackoverflow.com/questions/69556945/adding-application-insights-on-blazor-client-web-assembly

https://learn.microsoft.com/en-us/answers/questions/1384497/blazor-8-support-for-application-insights

https://github.com/IvanJosipovic/BlazorApplicationInsights

log works fine but when check logs in azure application insights at the time loggers are maintained by azure but where exception occured like Line number and path or file name missing at production

but i need both for slove the issue where the issue happened but method names shown in application insights

Please help me.

Thank you.

JasonPan - MSFT 7,021 Microsoft External Staff

Hi @ramesh P,

I can find the Line number and path or file name in the Details column. By the way, I am using exceptions table. Is that what you mean by locality? I'm going to try to publish Azure App Service.

User's image

I am using the repo you shared, here is the details.

[{"severityLevel":"Critical","outerId":"0","message":"NotImplementedException: Something wrong happened :(","type":"NotImplementedException","id":"0","parsedStack":[{"assembly":"at BlazorApplicationInsights.Sample.Components.TestComponents.TrackGlobalException() in E:\\temp\\samples\\BlazorApplicationInsights.Sample.Components\\TestComponents.razor.cs:line 47","method":"<no_method>","level":0,"line":0,"fileName":"47"},{"assembly":"at Microsoft.AspNetCore.Components.EventCallbackWorkItem.InvokeAsync[Object](MulticastDelegate delegate, Object arg)","method":"<no_method>","level":1,"line":0,"fileName":"delegate"},{"assembly":"at Microsoft.AspNetCore.Components.EventCallbackWorkItem.InvokeAsync(Object arg)","method":"<no_method>","level":2,"line":0,"fileName":"arg"},{"assembly":"at Microsoft.AspNetCore.Components.ComponentBase.Microsoft.AspNetCore.Components.IHandleEvent.HandleEventAsync(EventCallbackWorkItem callback, Object arg)","method":"<no_method>","level":3,"line":0,"fileName":"callback"},{"assembly":"at Microsoft.AspNetCore.Components.EventCallback.InvokeAsync(Object arg)","method":"<no_method>","level":4,"line":0,"fileName":"arg"},{"assembly":"at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs, Boolean waitForQuiescence)","method":"<no_method>","level":5,"line":0,"fileName":"eventHandlerId"}],"rawStack":"System.NotImplementedException: Something wrong happened :(\n ---> System.InvalidOperationException: TEST INNER\n --- End of inner exception stack trace ---\n at BlazorApplicationInsights.Sample.Components.TestComponents.TrackGlobalException() in E:\\temp\\samples\\BlazorApplicationInsights.Sample.Components\\TestComponents.razor.cs:line 47\n at Microsoft.AspNetCore.Components.EventCallbackWorkItem.InvokeAsync[Object](MulticastDelegate delegate, Object arg)\n at Microsoft.AspNetCore.Components.EventCallbackWorkItem.InvokeAsync(Object arg)\n at Microsoft.AspNetCore.Components.ComponentBase.Microsoft.AspNetCore.Components.IHandleEvent.HandleEventAsync(EventCallbackWorkItem callback, Object arg)\n at Microsoft.AspNetCore.Components.EventCallback.InvokeAsync(Object arg)\n at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync(UInt64 eventHandlerId, EventFieldInfo fieldInfo, EventArgs eventArgs, Boolean waitForQuiescence)"}]

Best Regards

Jason

ramesh P 0 Reputation points

2025-04-04T08:00:49.5166667+00:00

{"assembly":"at sample_WebAssembly.Client.Pages.Ordering.holdorderwhenpay()","method":"<no_method>","level":0,"line":0}****{"assembly":"at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)","method":"<no_method>","level":1,"line":0,"fileName":"task"}

{"assembly":"at sample_WebAssembly.Client.Pages.Payment.Calculatecash()","method":"<no_method>","level":2,"line":0}

{"assembly":"at sample_WebAssembly.Client.Pages.Payment.<BuildRenderTree>b__84_2()","method":"<no_method>","level":3,"line":0}

{"assembly":"at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)","method":"<no_method>","level":4,"line":0,"fileName":"task"}

{"assembly":"at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )","method":"<no_method>","level":5,"line":0}

under details this is parsed stack. There is no line number and file name or path not shown but i need line number and path

1 answer

Your answer

ramesh P 0 Reputation points

2025-04-04T08:00:49.5166667+00:00

{"assembly":"at sample_WebAssembly.Client.Pages.Ordering.holdorderwhenpay()","method":"<no_method>","level":0,"line":0}****{"assembly":"at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)","method":"<no_method>","level":1,"line":0,"fileName":"task"}

{"assembly":"at sample_WebAssembly.Client.Pages.Payment.Calculatecash()","method":"<no_method>","level":2,"line":0}

{"assembly":"at sample_WebAssembly.Client.Pages.Payment.<BuildRenderTree>b__84_2()","method":"<no_method>","level":3,"line":0}

{"assembly":"at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)","method":"<no_method>","level":4,"line":0,"fileName":"task"}

{"assembly":"at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )","method":"<no_method>","level":5,"line":0}

under details this is parsed stack. There is no line number and file name or path not shown but i need line number and path

Answer 1

Bruce (SqlWork.com) 75,051

The line numbers are in the symbol file (.pdb). Blazor WASM does not have code to load the symbol file and process on exceptions. In debug mode the debugger loads the symbol file and provides the translation of address to line number.

note: in .net core, you need is disable code optimization for the line numbers to be accurate.

ramesh P 0 Reputation points

2025-04-05T11:16:20.7433333+00:00

<DebugType>embedded</DebugType>

<DebugSymbols>true</DebugSymbols> I had used this in.csproj file for load pdb files to get line number and path or file name but not get. How to achieve this
Bruce (SqlWork.com) 75,051 Reputation points

2025-04-07T16:00:49.9033333+00:00

currently neither the Blazor WASM runtime nor AOT generated code support this feature.
ramesh P 0 Reputation points

2025-04-09T16:43:14.89+00:00

Can i pass the exception blazorWASM application to blazorsever for use loggers or telmeteryclient on blazorHostedWASM application. Is this capture the line number and filename where the exception occcured.
ramesh P 0 Reputation points

2025-04-10T11:56:11.17+00:00

You had reached the logs for blazorWASM application.Already you had shared the screen shots for line number and filename . I need how you achieve this. what reference link used for get line number and file name i need that. what you had done for get line number and file name where the exception occured
Bruce (SqlWork.com) 75,051 Reputation points

2025-04-10T19:20:34.75+00:00

The line number in the stack trace is done by the runtime mapping the exception stack address to the symbol table. This feature in not in the blazor WASM runtime nor AOT generated code.

you will need to refine your error reporting.

Share via

Line number and path or file name missing when logs maintain in azure applicationinsights for blazorWASM application

1 answer

Your answer