-
Notifications
You must be signed in to change notification settings - Fork 249
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
Support OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT
and OTEL_ATTRIBUTE_COUNT_LIMIT
#1251
Labels
good first issue
Good for newcomers
spec-compliance/v1.6.0
spec-compliance
Required for OpenTelemetry spec compliance
Comments
ahayworth
added
spec-compliance
Required for OpenTelemetry spec compliance
spec-compliance/v1.6.0
labels
May 11, 2022
We have the trace-specific versions of these ( opentelemetry-ruby/sdk/lib/opentelemetry/sdk/trace/span_limits.rb Lines 34 to 40 in 113e513
|
ahayworth
added a commit
to ahayworth/opentelemetry-ruby
that referenced
this issue
Jun 4, 2022
Fixes open-telemetry#1251 by additionally supporting `OTEL_ATTRIBUTE_COUNT_LIMIT` and `OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT` as ways to configure span limits. As per spec, the existing model-specific limits (eg: `OTEL_SPAN_ATTRIBUTE_...` env vars) are preferred when they are present. The easiest way to do this was to re-use the handy `config_opt` method in `opentelemetry-common` package, on which we already depend. It made the lines even longer, which is gross, but it works pretty nicely.
fbogsany
added a commit
that referenced
this issue
Jun 21, 2022
Fixes #1251 by additionally supporting `OTEL_ATTRIBUTE_COUNT_LIMIT` and `OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT` as ways to configure span limits. As per spec, the existing model-specific limits (eg: `OTEL_SPAN_ATTRIBUTE_...` env vars) are preferred when they are present. The easiest way to do this was to re-use the handy `config_opt` method in `opentelemetry-common` package, on which we already depend. It made the lines even longer, which is gross, but it works pretty nicely. Co-authored-by: Francis Bogsanyi <francis.bogsanyi@shopify.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
spec-compliance/v1.6.0
spec-compliance
Required for OpenTelemetry spec compliance
Added in open-telemetry/opentelemetry-specification#1130
We were early adopters of some of these limits, but they are not formalized in the spec and we should update.
The text was updated successfully, but these errors were encountered: