You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to control exactly which frame are traced in Jaeger? I mean explicitly choose which are traced, and which are not.
I have a use case with ~20 streams in which I skip processing for 99% of frames by removing the primary ROI. The frames which are kept are tagged in frame_meta.telemetry_span, so that I can search only for them in Jaeger traces. However, 99% of all Jaeger traces are now useless, since I'm only interested in the 1% frames which were actually processed. With random sampling=100, I hit too few of the useful 1% traces, so I have to sample more often, which overloads Jaeger.
Is there a way to, say, delete the telemetry_span for a frame and have it not traced in Jaeger, or something like this?
The text was updated successfully, but these errors were encountered:
Could you tell me what is the predicate (in your case), specifying which frame must be sent to a tracing system or not?
Telemetry span is created before any processing, I will check if it could be cancelled late or not with OTLP API. Probably, if you want to cancel it "late" it could be impossible to implement easy way.
I think you need to use the OpenTelemetry collector for traces and filter them based on your predicate. The traces you need you send to the Jaeger or another persistent storage, others are dropped.
Savant develop switched to OpenTelemetry format (not deprecated Jaeger) so you can feed the traces to OTLP collector and filter them.
Is there a way to control exactly which frame are traced in Jaeger? I mean explicitly choose which are traced, and which are not.
I have a use case with ~20 streams in which I skip processing for 99% of frames by removing the primary ROI. The frames which are kept are tagged in frame_meta.telemetry_span, so that I can search only for them in Jaeger traces. However, 99% of all Jaeger traces are now useless, since I'm only interested in the 1% frames which were actually processed. With random sampling=100, I hit too few of the useful 1% traces, so I have to sample more often, which overloads Jaeger.
Is there a way to, say, delete the telemetry_span for a frame and have it not traced in Jaeger, or something like this?
The text was updated successfully, but these errors were encountered: