Global error handler cleanup - exponential histogram

[lalitb]

Fixes #
Design discussion issue (if applicable) #

Changes

Please provide a brief description of the changes here.

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)

[lalitb]

Cijo's comment:
Unless we are 100% sure this cannot cause flooding of logs, lets remove the log from here, and leave a TODO to add logging once we understand more.

[lalitb]

I prefer to log as otel_debug till we are not sure.

[codecov]

Codecov Report

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

Project coverage is 79.5%. Comparing base (0202299) to head (0a39b3b).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...-sdk/src/metrics/internal/exponential_histogram.rs	0.0%	2 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2235   +/-   ##
=====================================
  Coverage   79.5%   79.5%           
=====================================
  Files        121     121           
  Lines      21113   21112    -1     
=====================================
  Hits       16803   16803           
+ Misses      4310    4309    -1     

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

[cijothomas]

these configs are too much information, so better skip it.

[lalitb]

I think max_size, min_scale, value and message should be kept, rest can be removed.

[cijothomas]

Okay to merge as exponential histogram is unlikely to declared stable soon (as it requires views), so we can revisit the comments later.

[TommyCpp]

It seems the naming convention is CamelCase. for log names. Is there a reason here?

[lalitb]

There are no specific reasons; it simply offers clearer visibility and effectively represents hierarchy when combined with dots. For example, ExponentialHistogramDataPoint.Scale.Underflow seems better to exponentialhistogramdatapoint.scale.underflow or exponential_histogram_datapoint.scale.underflow.

Or better example to represent hierarch would be LoggerProvider.Drop.ShutdownMutexPoisoned as compared to loggerprovider.drop.shutdownmutexpoisoned
But happy to change if there are specific guidelines/preferences.

[lalitb]

@TommyCpp - I am merging this to unblock. If there are specific recommendations, we can cover separately as this will affect throughout.

[cijothomas]

We can get some inputs from OTel Events team recommendations. Our event name is same as what OTel Events are. (There are lot of ongoing discussions in this area, so we need to comeback to this once things are more settled)