#support

Filtering Entry Level Spans in Signoz Traces

TLDR Arnab wants to filter entry level spans in Signoz traces. Ankit suggests raising an issue to check its implementation possibility.

10mo

Join the chat

Feb 19, 2023 (10 months ago)

Photo of md5-e1a0ebb2bd3143486204cc2a6d5b7e55

Arnab

07:44 AM

Hi team, in Signoz traces I see all of these traces, some of which are child spans, e.g. - middleware - urlEncodedParser — I only want to see the entry level spans here, and not spans that are part of some other trace. How can I get that?

Image 1 for Hi team, in Signoz traces I see all of these traces, some of which are child spans, e.g. - `middleware - urlEncodedParser` — I only want to see the entry level spans here, and not spans that are part of some other trace. How can I get that?

Photo of md5-dbe7088320fe1d922707613e02f3420d

Ankit

11:14 AM

Arnab got it...can you raise an issue for this. Will check if this can be implemented and added to sprint

Arnab

11:57 AM

Sure. Will do

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Issue with Missing Spans in Signoz Traces

Ali is facing an issue with missing spans in Signoz traces. vishal-signoz inquired about the instrumentation library being used and advised switching to the official java opentelemetry agent.

4mo

Resolving Log Parsing Issue in Python OpenTelemetry

Diogo was experiencing issues with log tracing in Python OpenTelemetry. nitya-signoz suggests parsing trace_id and span_id from the log message body or using pipelines feature. Despite partial success, Diogo continued to experience issues with `trace_id`.

Issue with Missing Spans in Trace in Signoz

Ali reported an issue with missing spans in a trace in Signoz, with code P01012 appearing twice, despite not taking any action. Palash tagged user vishal-signoz.

4mo