How do you search for relevant Traces? #71624
Replies: 4 comments 8 replies
-
I have worked with some different tools, which were typically self hosted log bucket style tools at big enterprise companies I worked at in the past, or AWS cloudwatch free tier bucket for my private (read useless) projects. I was a daily user and somewhat of a super user in my respective "tribe" for ELK stacks. These were my top workflows:
|
Beta Was this translation helpful? Give feedback.
-
By trace id. Which doesn't work because they are dynamically sampled out due the shear volume (we have ingest at 100%)
Trace id, and sometimes the variables in the URL or GraphQL call
I'm looking for errors, log messages, or DB calls
I do not. I'm generally focused on trouble a specific customer issue at a time
"Why did we return 500 to a customer?" "What happened with this external API call?" "How is a customer loading a page that dies before the backend finishes fetching the data?" |
Beta Was this translation helpful? Give feedback.
-
The Trace Search is available in Beta for all Orgs! Go to Explore->Traces to start searching your traces directly. Please let us know if you have any feedback 🙏 |
Beta Was this translation helpful? Give feedback.
-
Is there a way to search for traces via the Sentry API? https://docs.sentry.io/api/ I know the span attribute (key and value), I just want to use the API programmatically to get the related traces, and extract some timing info from them. |
Beta Was this translation helpful? Give feedback.
-
Traces can be quite helpful in debugging application problems in SSR frameworks like NextJS or problems that occur in one of the many distributed services powering your apps.
As such, finding the right trace makes debugging a lot easier. We’re working on enabling this workflow in Sentry.
Coming Soon: Trace Search!
We’ll soon ship a Trace search that lets you find traces with particular spans.
E.g. you can search for traces that have database spans that take over 2s
You’ll also be able to query traces with slow spans that impact a user who complained about slow experience:
Your feedback is much appreciated
As we work on enabling this Trace Search we’d love to get your take on the following questions:
Beta Was this translation helpful? Give feedback.
All reactions