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

(12 件のコメント) (1 件のリアクション) (0 人の担当者)Go (2,326 件のフォーク)batch import

enhancementgood first issuehelp wanted

Repository metrics

Stars: (18,974 個のスター)
PR merge metrics: (平均マージ 4d 11h) (30d で 85 merged PRs)

説明

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

コントリビューターガイド

調査方針: 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.
技術スタック: gogrpcrest api
領域: apibackendobservability
Issue 種別: 機能
難度: 3
推定時間: 1-2日
活動状況: アクティブ
明確さ: 明確
前提条件: Go programminggRPC basicsJaeger API fundamentals
初心者向け度: 45