jaegertracing/jaeger

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

Open

#7,594 创建于 2025年10月15日

在 GitHub 查看
 (12 评论) (1 反应) (0 负责人)Go (18,974 star) (2,326 fork)batch import
enhancementgood first issuehelp wanted

描述

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

贡献者指南

技术栈
gogrpcrest api
领域
apibackendobservability
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programminggRPC basicsJaeger API fundamentals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
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.