The available diagram is based on the traces you search for deep dependency graph.
Viewing a deep dependency graph
The deep dependency graph describes how the services in traces are connected based on the results of the trace search query you run. The graph lets you focus on the up and downstream hops of a service call and define the aggregation and graph density for the layout.
From the Jaeger deep dependency documentation , the deep dependency graph is...
...also known as “Transitive Dependency Graph”, where a chain
A -> B -> Cmeans that
Ahas a transitive dependency on
C. A single graph requires a “focal” service (shown in pink) and only displays the paths passing through that service. Typically, this type of graph does not represent the full architecture of the system, unless there is a service that is connected to everything, e.g. an API gateway, and it is selected as a focal service.
Use the deep dependency graph to view a partial graph relevant to your service of interest. This ability is genuinely useful when it’s not possible to view that service in a system architecture graph, especially if you have hundreds of services (or many more), where hovering to find a specific service isn’t feasible.
In the top right of the search results, click Deep Dependency Graph (next to the Sort drop-down). You can set which service to focus on as origin (in pink) and expand and collapse the levels in the diagram.
Enter a service or operation in the search box to highlight it in the deep dependency graph.