-
Notifications
You must be signed in to change notification settings - Fork 4
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
Convert span attribute values to strings #8
Comments
@sneako, it occurs to me another good point to get this fixed is at DataDog's end. Their API reference says only:
… and doesn't express much about what types the values might be. Perhaps they're open to casting all the values they get to strings at receipt time? |
I think it should be fixed in DD adapter. |
@hauleth When you say 'DD adapter' are you referring to the Datadog agent, or this library? |
This library. |
@sneako DD probably should fix either their agent or documentation as well, but we do not have control over these. Fixing it there is better solution for now. |
I have also opened a ticket with Datadog's support team to improve their documentation or the agent. Thanks everyone! |
Datadog has updated their docs as well DataDog/documentation#4609 |
As we discovered during opencensus-beam/opencensus_datadog#8, OpenCensus span attribute values [MUST] be one of: * an integer * a number * a string * a boolean `:oc_trace.start_span/3` won't crash if we give it an attribute value of `%Absinthe.Type.List{of_type: :string}`, but anything upstream encoding to JSON or OpenCensus protobuf certainly will. I've also renamed the attribute keys (also strings!) to match the period delimited style used by `Opencensus.Plug.Trace`. [MUST]: https://tools.ietf.org/html/rfc2119#section-1
As reported in opencensus-beam/opencensus_absinthe#10:
If DataDog can't cope with numbers, I think we'd better fix that in our DataDog adapters, because it doesn't make sense to change the rest of the OpenCensus ecosystem to cast attributes to strings just in case the spans might get sent to DataDog.
Nailing it down a little:
The text was updated successfully, but these errors were encountered: