Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trace explorer: Add support for stacktraces that appear in the "Stacktraces" tab in trace explorer #26979

Open
scrooloose opened this issue Aug 21, 2024 · 1 comment
Assignees

Comments

@scrooloose
Copy link

Hello, at work we are using trace explorer in one of our Ruby on Rails apps. It is quite useful. However, the stacktraces for each span are shown as json objects in the span's Attributes tab, rather than in the actual Stacktraces tab.

image

Currently, to find the line of our app code that generated the span, we have to copy/paste the stacktrace json out and run it through a tool like jq.

I notice that the library is just setting the stacktrace as a label on the span, but it looks the API to create spans does have a place to put proper stacktraces? https://cloud.google.com/trace/docs/reference/v2/rest/v2/projects.traces.spans/createSpan.

First question:

  1. Is it possible to configure the library to populate the Stacktraces tab in the UI instead of using a label on the span? I'm prepared to believe I'm just misconfiguring the library somehow :-)
  2. If it is not possible to populate the Stacktraces tab, are there plans to update this? Do you accept pull requests?

Thanks!

@scrooloose scrooloose changed the title Add support for stacktraces that appear in the "Stacktraces" tab in trace explorer trace explorer: Add support for stacktraces that appear in the "Stacktraces" tab in trace explorer Aug 21, 2024
@scrooloose
Copy link
Author

After some further investigation, it looks like the google-cloud-trace gem has two version specific companion gems (v1 and v2), and it looks like the base gem is hardcoded to use v1? Is this correct? Can it be configured to use v2 or is that simply not possible at this stage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants