[exporter/debug] feat: add dropped* attributes to output

[khpeet]

Description

Added logging output for:

• DroppedAttributesCount
• DroppedEventsCount
• DroppedLinksCount

Link to tracking issue

Fixes #14202

Testing

Added validation output to two_spans.out and traces_with_entity_refs.out

Documentation

Added changelog yaml entry summarizing the issue and fix.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.16%. Comparing base (8f51a17) to head (3367501).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14217      +/-   ##
==========================================
- Coverage   92.17%   92.16%   -0.02%     
==========================================
  Files         668      668              
  Lines       41510    41513       +3     
==========================================
- Hits        38262    38260       -2     
- Misses       2215     2218       +3     
- Partials     1033     1035       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[andrzej-stencel]

Thanks @khpeet for this contribution 🙏 I have one suggestion for the ordering, please let me know what you think.

[khpeet]

Thanks for the review @andrzej-stencel - fixed!

[andrzej-stencel]

Thanks!

[andrzej-stencel]

This is a bit verbose, I'd rather have buf.logAttr("DroppedAttributesCount", span.DroppedAttributesCount()), but this currently results in funny output like DroppedAttributesCount: %!s(uint32=0). Would be nice to fix the logAttr method in a separate change.

[codspeed-hq]

CodSpeed Performance Report

Merging #14217 will not alter performance

_{Comparing khpeet:main (3367501) with main (8f51a17)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 59 untouched
⏩ 20 skipped¹

Footnotes

1. 20 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[otelbot]

Thank you for your contribution @khpeet! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.