Why maximum dependency length is set to 100 in DAG?

[egorzekov]

jaeger-ui/src/components/DependencyGraph/index.js

Line 88 in 85f9822

if (dependencies.length <= 100) {

Hello jaeger development team.

We are using your project and we appreciate your work!
Unfortunately, we faced one issue and came to decision to ask you.

The question is "Why maximum dependency length is hard-coded to 100 in DAG?".

if (dependencies.length <= 100) {
      GRAPH_TYPE_OPTIONS.push({ type: 'DAG', name: 'DAG' });
}

In our project we have a lot of cases with 100+ dependencies and due to this limitation DAG can't be shown.

Thanks in advance.

[yurishkuro]

Iirc it's because for large graphs that layout doesn't work well

[egorzekov]

Could you please do this setting configurable?

[tiffon]

@egorzekov A config setting has been added for this. It's will be released in 1.1.0, which is being prepped:

jaegertracing/jaeger#612

The config setting is dependencies.dagMaxNumServices. The UI config docs are here. The specific setting is not added to the docs, yet, but the following config JSON would change the max to 200:

{
  "dependencies": {
    "dagMaxNumServices": 200
  }
}