Skip to content

Consider consuming non-supported attribute value types #1509

Open
@carlosalberto

Description

For dynamic languages, SetAttribute() MAY end up getting a value of an unsupported type. Current implementations simply ignore the value, but was wondering whether it could be good to do a best-try effort and simply convert the value to string (which is something we did in OpenTracing).

Arguably this will mean having different output, but we haven't frozen the telemetry compatibility section.

Metadata

Assignees

No one assigned

    Labels

    area:apiCross language API specification issuespec:traceRelated to the specification/trace directory

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions