-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Exporter.OpenTelemetryProtocol] SdkOptionLimits - fix defaults #3978
[Exporter.OpenTelemetryProtocol] SdkOptionLimits - fix defaults #3978
Conversation
94c42dc
to
0c215d6
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3978 +/- ##
==========================================
- Coverage 85.58% 85.54% -0.05%
==========================================
Files 288 288
Lines 11070 11080 +10
==========================================
+ Hits 9474 9478 +4
- Misses 1596 1602 +6
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. We'd originally punted on adopting the defaults because technically this could be considered a breaking change. Though, I'm not really concerned 128 is a pretty generous default and I'd suspect have low chance of impacting many users. Also, I think it's fair to frame this as a bug fix.
* Bump OTel to 1.4.0-rc.1 * ConfigureResource api was removed in open-telemetry/opentelemetry-dotnet#3999 * Update limits based on open-telemetry/opentelemetry-dotnet#3978 * Fix build structure OpenTelemetry references OpenTelemetry.Extensions.DependencyInjection package * Fix ModuleTests * Handle AspNetCore metrics changes
Fixes #3962.
Changes
Fix default values for
OTEL_ATTRIBUTE_COUNT_LIMIT
,OTEL_ATTRIBUTE_COUNT_LIMIT
,OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT
,OTEL_SPAN_EVENT_COUNT_LIMIT
,OTEL_SPAN_LINK_COUNT_LIMIT
,OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT
,OTEL_LINK_ATTRIBUTE_COUNT_LIMIT
. All of them are defaulted to128
.CHANGELOG.md
updated for non-trivial changes[ ] Design discussion issue #[ ] Changes in public API reviewed