jaegertracing/jaeger

query service "search" api 'limit', 'total' and 'offset' fields are not supplied on response

Open

#2027 opened on Jan 17, 2020

View on GitHub
 (17 comments) (3 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
area/storageenhancementhelp wanted

Description

Requirement - what kind of business use case are you trying to solve?

set of fields are not supplied on the query service search response

Service: jaeger query API: /apt/traces Current response:

{
  data: "...",
  total: 0,
  limit: 0,
  offset: 0
}

Response struct: https://github.com/jaegertracing/jaeger/blob/886b96574253a005ee7ebe74140098f3fe183606/cmd/query/app/http_handler.go#L56 Response part: https://github.com/jaegertracing/jaeger/blob/886b96574253a005ee7ebe74140098f3fe183606/cmd/query/app/http_handler.go#L238

Fields total, limit and offset are not supplied on the response part.

I am ready yo submit a PR if someone guide me to get these fields.

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programming basicsFamiliarity with Jaeger query service
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue reports that the `/api/traces` response is missing `total`, `limit`, and `offset` fields. The response struct is defined in `cmd/query/app/http handler.go` at line 56, and the response is constructed at line 238. The developer should investigate how these fields are computed from the query result and ensure they are included in the response. The existing comments may contain hints, but maintainers should clarify the expected values. A good first step is to examine the data returned by the query service and confirm the source of these fields.