jaegertracing/jaeger

[Feature]: Add support to query for dependencies in api/v3 API

Open

#7595 opened on Oct 15, 2025

View on GitHub
 (5 comments) (1 reaction) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
area/storageenhancementgood first issuehelp wanted

Description

Requirement

In Grafana to be able to visualize the dependency graph we are using api/dependencies. We are trying to migrate to api/v3 but it does not seem like this supports querying for dependencies.

Problem

We are unable to migrate away from the internal API for dependency graph without the support of dependencies in the api/v3/* endpoint

Proposal

Add support to query for dependencies in the api/v3/ endpoint.

Open questions

No response

Contributor guide

Tech stack
gorest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingREST API designJaeger architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
First, review the existing internal API endpoint `api/dependencies` in `cmd/query/app/` and its implementation. Then, examine the `api/v3` swagger specification at `https://github.com/jaegertracing/jaeger idl/blob/main/swagger/api v3/query service.swagger.json` to understand the expected endpoint structure. Look at how other endpoints in `api/v3` are implemented, such as `api/v3/services`. Check any discussions or linked PRs in this issue for guidance on implementation.