Stack trace is not formatted correctly in stackdriver

[igorwwwwwwwwwwwwwwwwwwww]

Hi!

We're using the stackdriver exporter, and it looks like there is some kind of mismatch in the formatting of the stack trace data.

We get this kind of messy output:

I'm not sure what exactly is up there. It might be a snake_case vs camelCase thing. i.e. stackFrames vs stack_frames.

We're currently working around it by reducing default_max_stack_frames, since otherwise some attributes may get pushed below the scrollable portion of the page.

I believe having proper formatting of the stack traces would greatly improve the UX here.

Thanks!

[dazuma]

Thanks for the report. I've verified that the exporter is sending the correct protobuf, and so I've forwarded this to the Stackdriver UI team (internal bug 80152470).

[igorwwwwwwwwwwwwwwwwwwww]

Hi, I was wondering if there was any update on this front. Thanks!

[danielmbarlow]

@dazuma Is this perhaps the format expected by the Google Trace API?
https://github.com/googleapis/google-cloud-ruby/blob/e0bcff9509519d0e96b39c0fae54c3f942cf30c9/google-cloud-trace/test/google/cloud/trace/notifications_test.rb#L55