Handling NaN, Infinity, -Infinity in string representation of complex attributes

[trask]

Component(s)

pdata

Describe the issue you're reporting

Recent specification suggested string representation of complex attributes for non-OTLP protocols aligns with the Collector's pdata Value AsString, except for the representation of NaN, Infinity, and -Infinity.

I thought I could just update float64AsString but quickly realized that the bigger problem is that json.Marshal is used for maps and lists, which doesn't support these values.

And I'm not sure if it's worth replacing the usage of json.Marshal just to handle these edge cases.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• pdata: @bogdandrutu @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[mx-psi]

Apologies, I missed this detail. I think we can at least update float64AsString to make one more step towards compliance. I agree that replacing the usage of json.Marshal seems less justified.