ILogger.LogError produces empty line in "monitor" panel

[WinInsider]

The "Exception" argument of ILogger.LogError(...) method produces empty line in "monitor" panel in Azure Portal, instead printing out exception stack trace.

Example

[brettsam]

@WinInsider -- can you share exactly which overload you're using here?

[WinInsider]

Invoked via this) extension method

Eg: logger.LogError(e, "Failed to save record");

What comes out in "monitor" panel (in Azure Portal) is two lines, first one is blank, second line would have "Failed to save record". Without details in first line as to the exception that has occurred.

[kshyju]

@WinInsider Do you see the same empty line entry when you query the app insights logs/tables?

[WinInsider]

Yes same,

However, the error details can be found in App Insights blade/area, under "Failures/Exceptions"... the downside is that is not easy to corollate the exception if there are many errors.

Prehaps is worth noting the type of exception, AggrigatedException, as a result of async/await operation. Maybe there is a difference in the way the new azure function sdk handles AggrigatedException.

[kshyju]

Thanks! I was able to repro this issue. It seems like a glitch in the JOIN query used to render the monitor tab data. If you query the raw data (traces or exceptions tables), you will not see an empty entry logged. Will follow up with the team and share an update here and the next steps to fix it.

cc @brettsam

[brettsam]

cc @spellegrino021, @takyyon -- looks like we need to tune the query that we generate here. The data is there, it just gets lost in the union.

The details are above, but @kshyju has a repro that he should be able to share too.

[WinInsider]

Have run app insights query against exceptions however, there is no "message" element/property thus still comes up empty/blank for me.

I have notice this behavior only after switching to new Azure Function Worker SDK (Microsoft.Azure.Functions.Worker)

Could it be the case that message on this line is null or empty?

[fabiocav]

@mattchenderson , we need to follow up with the UX folks on this.

[stevencreaney]

Is there any progress on this? or a workaround to get the Exceptions logged properly in the Monitor view?

[djfoz]

I'm also encountering this issue.

[anudeeparavapalli]

Hi, is this issue solved?