Not all exceptions are populated with exception type and message

[ivan-zaitsev]

Not all exceptions are populated with exception type and message

[heyams]

@ivan-zaitsev did you see exception.type and exception.message in the Application Insights logs blade remoteDependencies table?
We've checked the code, this log didn't represent the actual custom dimensions to application insights. exception.type and exception.message should be parsed automatically by opentelemetry trace sdk. Please let me know.

[ivan-zaitsev]

Hello @heyams Correct it doesn't represent the actual custom dimensions to application insights and I didn't see fields exception.type and exception.message in Azure Insights dependencies table.

I have custom extension which processes span events and it relies on exception.type and exception.message. Seems that the telemetry exporter behaves differently when exception is propagated to main thread it adds exception.type and exception.message, but when it is not propagated it adds different field - exception.

Currently because of this inconsistent behavior I need to cover two cases because Azure Blob Storage client library sometimes throws exactly identical exception to main thread for example for find operations and sometimes it catches exception for example for exist operations.

[heyams]

@ivan-zaitsev exception.type and exception.message are added to custom dimensions by getAttributes() https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/internal/data/ImmutableExceptionEventData.java.

I will use your code to reproduce it or if you can push a repro app to https://github.com/microsoft/ApplicationInsights-Java-Repros will help too.

[ivan-zaitsev]

@heyams In case of code above To Reproduce when exception is not propagated to main thread exception.type and exception.message will not be added.