-
Notifications
You must be signed in to change notification settings - Fork 252
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
Add support for array-valued attributes #160
Comments
As long as I'm looking at this: There seem to be a number of places where the type of Should I add validation in these places, raising |
Having the observability system raise runtime exceptions is frowned upon see: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/error-handling.md. The preferred approach is to use defaults or discard data that doesn't conform and log a message about it. |
Another trend you may notice, is that validating data can sometimes be expensive to do up front, and since data is sampled, it often is more efficient to validate, drop or correct data on export. |
* Add support for array-valued attributes. Resolves #160. * Update documentation of Trace::Span#add_event. * Test that Trace::Span#add_event can handle empty array values. * Optimize SDK::Internal::valid_array_value? * Rename SDK::Internal::valid_primitive_value? to valid_simple_value? * Tiny change to overcome github.com issue. * Extract Jaeger::Exporter::SpanEncoder class. * Add tests for Jaeger::Exporter::SpanEncoder. * Jaeger::Exporter::SpanEncoder handles array attributes. * Fix rubocop issues. * Reduce complexity of SpanEncoder#encoded_tags.
See open-telemetry/opentelemetry-specification#368
The text was updated successfully, but these errors were encountered: