[GenevaExporter] Add ability to export Log Exception using StackTrace

[cijothomas]

Changes

Adds a new option to use StackTrace property of Exception be used while exporting Logs.
Fixes #2421

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
• Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes
• Changes in public API reviewed (if applicable)

[CodeBlanch]

LGTM

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (71655ce) to head (3cc969b).
Report is 662 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #2422       +/-   ##
==========================================
- Coverage   73.91%       0   -73.92%     
==========================================
  Files         267       0      -267     
  Lines        9615       0     -9615     
==========================================
- Hits         7107       0     -7107     
+ Misses       2508       0     -2508     

see 263 files with indirect coverage changes

[reyang]

I don't understand the direction here, if this is what we want to give to the user, what's the plan for other exporters (e.g. OTLP)?

[cijothomas]

I don't understand the direction here, if this is what we want to give to the user, what's the plan for other exporters (e.g. OTLP)?

Otel SDK has to offer mechanism to let user pick how they want stack trace represented.
Activity in runtime already offer mechanism to let user decide this. ILogger does not, but the change would likely be in Otel SDK/Exporter, as ILogger hands the Exception object itself to the providers.

[reyang]

I don't understand the direction here, if this is what we want to give to the user, what's the plan for other exporters (e.g. OTLP)?

Otel SDK has to offer mechanism to let user pick how they want stack trace represented. Activity in runtime already offer mechanism to let user decide this. ILogger does not, but the change would likely be in Otel SDK/Exporter, as ILogger hands the Exception object itself to the providers.

Is there a tracking issue and design discussions? My concern is around the lack of overall design/thinking. I don't see why we want to rush here.

[cijothomas]

I don't understand the direction here, if this is what we want to give to the user, what's the plan for other exporters (e.g. OTLP)?

Otel SDK has to offer mechanism to let user pick how they want stack trace represented. Activity in runtime already offer mechanism to let user decide this. ILogger does not, but the change would likely be in Otel SDK/Exporter, as ILogger hands the Exception object itself to the providers.

Is there a tracking issue and design discussions? My concern is around the lack of overall design/thinking. I don't see why we want to rush here.

Nothing open in Otel .NET repo, but spec has seen asks before on having the ability to control the strackTrace representation:
open-telemetry/opentelemetry-specification#2839