Is there an API for Jaeger's Deep Dependency Graph feature?

[ez4r1sk]

The Deep Dependency graph feature helps me to visualize the workflow of how different services interact with each other and relations between them. I find it better than the System Architecture graph although both are from the trace data, also the Layout settings are very useful to extract a minimal workflow of a particular program.

Wanted to know if there is some kind of API that would help extract this graph with just some tags?

[dosubot[bot]]

Hey @ez4r1sk! I'm here to help you with your question. Let's figure this out together!

Yes, there is an API for Jaeger's Deep Dependency Graph feature. You can use the fetchDeepDependencyGraph method to extract this graph using tags.

Here is the relevant code snippet:

fetchDeepDependencyGraph(query) {
  return getJSON(`${ANALYTICS_ROOT}v1/dependencies`, { query });
}

This method allows you to fetch the deep dependency graph by passing the appropriate query parameters. The Deep Dependency Graph, also known as the "Transitive Dependency Graph," shows a chain A -> B -> C meaning that A has a transitive dependency on C. A single graph requires a "focal" service and only displays the paths passing through that service. The node granularity of this graph can be changed between services and service endpoints. At this time, the transitive graph can only be constructed from traces in the search results. In the future, there will be a Flink job that will compute the graphs by aggregating all traces.

For more details, you can refer to the Jaeger documentation ^[1][2][3][4].

To continue talking to Dosu, mention @dosu.

[ez4r1sk]

@dosu can your provide a sample example of an API call to the v1/dependencies. I am wondering what information we would need to pass on query part

[dosubot[bot]]

To make an API call to the v1/dependencies endpoint, you need to pass two parameters in the query part of the URL:

1. endTs - the end of the time interval (number of milliseconds since epoch).
2. lookback - the length of the time interval in milliseconds (i.e., start-time + lookback = end-time).

Here is a sample example of an API call to the v1/dependencies endpoint:

curl -G 'https://jaeger-query:16686/api/dependencies' \
     --data-urlencode 'endTs=1633024800000' \
     --data-urlencode 'lookback=86400000'

In this example:

• endTs=1633024800000 represents the end of the time interval in milliseconds since epoch.
• lookback=86400000 represents the length of the time interval in milliseconds (1 day in this case).

The returned JSON is a list of edges represented as tuples (caller, callee, count). For programmatic access to the service graph, the recommended API is gRPC/Protobuf. Note that the HTTP JSON API is intended for internal use and is subject to change ^[1][2][3][4].

To continue talking to Dosu, mention @dosu.