Add stress-test framework to contrib repo.

[lalitb]

Changes

I believe it would be benefitial to have stress framework copied from main to the contrib repo, to enable packages from this repo do necessary tests.

Have added the framework, along with the sample stress test for user-events enabled. The stress test result for user_events can be discussed separately in #133.

Ps. - It would be difficult to keep stress framework in sync between the two repos. I don't see any other easy way as of now, unless we publish the framework as a separate crate. But this would incur added responsibility in maintaining it.

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 126 lines in your changes missing coverage. Please review.

Project coverage is 54.3%. Comparing base (4f2ac34) to head (c2a825f).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
stress/src/throughput.rs	0.0%	117 Missing ⚠️
stress/src/user_events_enabled.rs	0.0%	9 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #138     +/-   ##
=======================================
- Coverage   55.4%   54.3%   -1.2%     
=======================================
  Files         39      41      +2     
  Lines       6101    6227    +126     
=======================================
  Hits        3384    3384             
- Misses      2717    2843    +126     

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

[cijothomas]

couple of suggestions

1. Lets add one test with and without tracepoint being enabled.
2. Instead of testing just the event header, lets test via OTel itself, so we know the overall cost/contention, not just that of EventHeader crate.

[lalitb]

Lets add one test with and without tracepoint being enabled.

Yes, I thought about it. This needs some thinking, as there needs to be some listener for the tracepoint. Can we do it as separate PR?

Instead of testing just the event header, lets test via OTel itself, so we know the overall cost/contention, not just that of EventHeader crate.

This test was specifically for cost incurred for eventheader crate. Plan is to add separate test for the actual export and enabled check through Otel.

[cijothomas]

if this is only testing event header (that should be done by that repo!), lets rename to "eventheader_enabled" / similar.

[cijothomas]

It's okay to copy the stress test logic for now. (I think .NET GitHub also does this !)
Looking forward to seeing more OTel exporter code being stress tested.

(left some non blocking comments, okay to follow up)