Skip to content

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

@jcolladokuri

Description

@jcolladokuri

Requirement

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

Image

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

Image

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementgood first issueGood for beginnershelp wantedFeatures that maintainers are willing to accept but do not have cycles to implement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions