jaegertracing/jaeger

[Feature]: Support parameters for attributes and limit in api/v3/traces endpoint

Open

#7594 opened on Oct 15, 2025

View on GitHub
 (12 comments) (1 reaction) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
enhancementgood first issuehelp wanted

Description

Requirement

When using Jaeger UI search filtering through tags and limiting the number of results is supported:

Grafana provides a similar experience but is using the internal HTTP endpoint which is not recommended.

We are working on migrating to the HTTP /api/v3/* endpoint but this does not support filtering with tags (attributes) or limiting the number of results.

It appears that the gRPC service does allow a parameter for attributes

Problem

Without the parameters for tags (attributes) or limit we are unable to migrate to api/v3/traces for searching trace results.

Proposal

Add support for attributes and limit parameter in the api/v3/traces endpoint.

Open questions

No response

Contributor guide

Tech stack
gogrpcrest api
Domain
apibackendobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programminggRPC basicsJaeger API fundamentals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the current implementation of the api/v3/traces endpoint in the Jaeger backend, particularly the gRPC query service methods. Review the protobuf definitions in query service.proto to understand the existing attributes parameter and how to pass it through the HTTP gateway. Examine the Grafana plugin's use of internal HTTP endpoints to see how filters are currently applied. Consider adding query parameters for attributes and limit to the HTTP handler and ensuring they propagate to the gRPC service.