jaeger trace api with date filter

[HiteshDhuria]

I have jaeger V2 backed with elasticsearch and using Traces query to get a specific trace id. How do I give date or time filter here to optimize search since just with traceid alone it seems to be taking longer as its searching all indexes.

[dosubot[bot]]

Hola @HiteshDhuria! 👋 Soy un bot aquí para ayudarte a resolver errores, responder preguntas y convertirte en un contribuyente. Estoy disponible mientras esperas a un mantenedor humano. ¡Vamos a solucionar esto juntos! 🚀

To apply a date or time filter when querying a specific trace ID in Jaeger, you can use the optional time window feature. This involves specifying the start_time and end_time fields in the GetTraceParams message. These fields allow you to define a time interval for the search, which can help optimize the query by narrowing down the search to specific indices.

Here's an example of how you might structure the GetTraceParams message:

message GetTraceParams {
  bytes trace_id = 1; // Your trace ID here
  google.protobuf.Timestamp start_time = 2; // Optional start time
  google.protobuf.Timestamp end_time = 3; // Optional end time
}

By providing values for start_time and end_time, you can limit the search to a specific time window. If these fields are not provided, the search will not be restricted by time ^[1].

Additionally, when using Elasticsearch as the backend, keep in mind that the start and end parameters should be expressed in microseconds since the Unix epoch ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[dosubot[bot]]

To filter traces by time using the Jaeger API, ensure that the start and end parameters are correctly formatted as microseconds since the Unix epoch. Your URL seems to be correctly formatted in this regard. However, make sure that the trace ID and other parameters are correctly specified and that the time range actually contains the trace you're looking for.

Additionally, verify that your Elasticsearch backend is properly configured to handle these queries. You might need to check configurations such as es.max-span-age and es.timeout to ensure they align with your query requirements ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yurishkuro]

ES storage currently does not respect the time range (none of built-in storages do, as a matter of fact, the capability was introduced for external grpc-based implementations)

jaeger/internal/storage/v1/elasticsearch/spanstore/reader.go

Line 245 in 04d2983

return s.multiRead(ctx, query, currentTime.Add(-s.maxSpanAge), currentTime)

[HiteshDhuria]

Hi @yurishkuro, Thank you so much for your quick response. Can we have a GetTraces override with time range so instead of just giving an option back from current time we can use start date and end date flexibility for better query performance?

[yurishkuro]

there is no need for override, the code just need to change to respect the timestamps if provided. Feel free to open a PR