This message was deleted.

Slackbot

08/05/2022, 12:55 PM

This message was deleted.

Vishal Sharma

08/05/2022, 1:05 PM

Hi @Cluas thanks for suggestion but I wanted to understand why do you need to search with trace id? cc: @Pranay

Ankit Nayan

08/05/2022, 1:27 PM

@Cluas as @Vishal Sharma mentioned, we want to understand more why do you want to search by traceID? • At trace filter page? If a traceID is filtered, it will only show spans from that traceID. So are the number of services and other filter suggestions helpful there? Or you want to choose a span from the spanList? • At trace detail page? If you have a traceID, you can change the URL for that traceID and you shall see the needed trace in trace detail page

Cluas

08/05/2022, 3:12 PM

This is a general pattern for troubleshooting problems, generally the front-end will give a traceID, and then the back-end according to this traceID to view the complete link, locate the problem link.

Cluas

08/05/2022, 3:13 PM

In jaeger, something like this.

Cluas

08/05/2022, 3:15 PM

The exact and unique request information that the client can provide is the TraceID, and it would be much easier if there was a query portal, but of course we can do this now by modifying the URL, and it would be more in line with the interaction habits if there is a search bar

Ankit Nayan

08/05/2022, 3:28 PM

got it

7 Views

Open in Slack

Previous Next

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.