`ILogger.LogError(Exception, string)` results in incorrect exception message in AppInsights

[richardszalay]

<PackageReference Include="Microsoft.Extensions.Logging.ApplicationInsights" Version="2.9.1" />

Steps to reproduce:

1. Setup a basic ASP.NET Core application
2. Configure AI using services.AddLogging(c => c.AddApplicationInsights())
3. Throw an Exception with the message "Actual exception message"
4. Catch the exception and log it to an injected ILogger using logger.LogError(ex, "Contextual message")
5. Review the exception in AI

Expected:

Both "Contextual message" and "Actual exception message" are presented in the exception object in AI

Actual:

Only "Context message" is included. The actual exception message is lost.

[cijothomas]

@richardszalay Can you use the latest (2.11.0) of the package and see if this is an issue?

[cijothomas]

There was this change: microsoft/ApplicationInsights-dotnet-logging#282

[btastic]

Is this related to this: #1807?

I am currently investigating why we don't see any exceptions when Logging with LogInformation(ex, "message") either.

AI Version: <PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.14.0" />
This is our code:

public async Task<bool> IsAvailableAsync()
{
	try
	{
		var response = await externalService.GetSomething();

		if (!string.IsNullOrEmpty(response.id))
		{
			return true;
		}
	}
	catch (TimeoutException)
	{
		_logger.LogInformation("Timeout exception when checking for ServiceAvailability.");
		return false;
	}
	catch (Exception ex)
	{
        // this happens, but AI is not logging exceptions
		_logger.LogWarning(ex, "Exception when checking for ServiceAvailability");
		return false;
	}

	return false;
}

Here is the details page of the "exception" log:

Is there anything we can do to solve this?

@TimothyMothra maybe you can add to this, whether this is the same as #1807

[joaopgrassi]

@btastic Just FYI, I hit this a while ago where Information logs were not being found on App Insights and it's due to this: https://github.com/MicrosoftDocs/azure-docs/issues/52657. Basically the ApplicationInsights log provider does not inherit from the "Default" log levels/categories.

[cijothomas]

@btastic Trying to understand the issue you are reporting more:
The following is your code:

// this happens, but AI is not logging exceptions
_logger.LogWarning(ex, "Exception when checking for ServiceAvailability");

ApplicationInsights is capturing the above as a TraceTelemetry and not as ExcepionTelemetry - is this what you are experiencing?

[chigivigi]

@cijothomas that is happening in my azure function. I am sending a LogError message, but it is written as a Trace in ApplicationInsights.

Azure Function v3, netcore 3.1

[cijothomas]

@cijothomas that is happening in my azure function. I am sending a LogError message, but it is written as a Trace in ApplicationInsights.

Azure Function v3, netcore 3.1

For functions - please post it in Functions repo, as Functions use a different integration with applicationinsights.

[github-actions]

This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[abisleem]

@cijothomas that is happening in my azure function. I am sending a LogError message, but it is written as a Trace in ApplicationInsights.
Azure Function v3, netcore 3.1

For functions - please post it in Functions repo, as Functions use a different integration with applicationinsights.

This is actually happening to me on .AspDotNetCore on .NetCore 3.1

[cijothomas]

@cijothomas that is happening in my azure function. I am sending a LogError message, but it is written as a Trace in ApplicationInsights.
Azure Function v3, netcore 3.1

For functions - please post it in Functions repo, as Functions use a different integration with applicationinsights.

This is actually happening to me on .AspDotNetCore on .NetCore 3.1

Please open a new issue in this repo, with the exact description of the expected behavior vs actual.

[abisleem]

I see that this unexpected behavior is brought up here as well #2471. I won't open a new issue to avert from creating duplicates.