Tyler Helmuth

@kernelpanic77 passing only the string isn't enough. The TransformContext will need access to the `ptrace`/`pmetric`/`plog` structs I mentioned before so that context can correct set the value. Dont start with...

@prabhatsharma I believe you're right, thank you for bringing this to our attention. In https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/kubeletstatsreceiver/internal/kubelet/network.go we use the bytes provided at the root of https://pkg.go.dev/k8s.io/kubelet/pkg/apis/stats/v1alpha1#NetworkStats. If we wanted to recorded...

Definitely a featureflag. Also I think we're in luck: the existing metric already defines `interface` as an attribute so I think we could do this without breaking the existing metric....

It would be a weird case, but technically a context someone creates could use `null` as a valid path name, so I don't think we want to do any special...

I agree that `set(attributes["test"], "value") where null == nil` is weird, and we'd never introduce `null` as a path in `pkg/ottl/contexts`, but I'm not convinced yet we should limit a...

@bryan-aguilar can you remind me of the situation you experienced that requires this function?

Closing for now. If anyone can come up with a way to produce `NaN` that would need checked please comment.

/cc @jinja2 @dmitryax @povilasv

@povilasv thank you!

@ChrsMark in my opinion yes to all questions. We want to be aligned with the spec (although I'd love to reduce the number of iterations in the receivers to gain...