Sanitize trace payload and transform to camel case for consistency
As pointed out in this comment, there is some inconsistent usage of camel/snake case in tracing UI ( snake case when accessing the traces payload directly and camelCase when accessing data that is been processed already )
To avoid confusion we can add a sanitation step when we receive the data from the API and transform it to camelCase so that it's consistent with everything else.
Or alternatively, just make it consistent and stick to snake_case when referring to traces/span API data
Also related to #2463 (closed) ( where the traces payloads also have some inconsistencies)
Edited by Daniele Rossetti