[otlp] Remove ilogger and exception attributes

[vishweshbankwar]

Fixes #
Design discussion issue #

Changes

This PR excludes the following fields on LogRecord from being exported by the OTLP exporter:

• EventId
• CategoryName
• Exception

Please provide a brief description of the changes here.

Merge requirement checklist

• CONTRIBUTING guidelines followed (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)

[codecov]

Codecov Report

Merging #4781 (559f26f) into main (77b3a1e) will decrease coverage by 0.10%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4781      +/-   ##
==========================================
- Coverage   85.46%   85.36%   -0.10%     
==========================================
  Files         314      314              
  Lines       12940    12930      -10     
==========================================
- Hits        11059    11038      -21     
- Misses       1881     1892      +11     

Files Changed	Coverage Δ
...etryProtocol/Implementation/LogRecordExtensions.cs	80.00% <ø> (-12.50%)	⬇️

... and 6 files with indirect coverage changes

[alanwest]

LGTM. One small thing to address regarding a test.

[CodeBlanch]

LGTM

[cijothomas]

its better if we add a stronger message here, as this is a significant breaking change for users who are relying on these features.

Breaking/Please Note or something to catch attention.

[samsp-msft]

Not having the EventId & Category properties makes it harder to filter log messages to the ones that you care about. They could go in the attributes as they are SDK specific.

[amccool]

Not having the EventId & Category properties makes it harder to filter log messages to the ones that you care about. They could go in the attributes as they are SDK specific.

+1

[austindrenski]

Not having the EventId & Category properties makes it harder to filter log messages to the ones that you care about. They could go in the attributes as they are SDK specific.

Indeed. Missed this in last week's release notes and ran into this today. Was a real head-scratcher for a few hours because this is the last place I expected these (fairly ubiquitous) dotnet attrs to be getting dropped ☹️