Netmap link traffic does not always show

[Etienne Lacombe]

Traffic on links in Netmap does not consistently show. Sometime, I refresh and I get most of the links showing traffic (green). Sometimes, none show. The call to /netmap/api/graph/layer2/1?traffic=1 occurs every time but does not display every time. Sometimes, only a few links have the traffic indicator showing, sometimes, almost all and sometimes none.

I'm using Firefox 30, latest version of NAV on a VM. VM CPU, response time is totally fine. That specific URL call takes >1 second (2759 ms, 1988ms, 2070ms). Time for the request does not seem to be the cause for the green to show or not show as the 2070ms showed most of the links while the 1988ms showed only a few and a 2192ms showed the most.

In the WebConsole, I get

- TypeError: mutating the [[Prototype]] of an object will ause your code to run very slowly;
- Use of getPreventDefault() is deprecated.

I don't know that any of those have anything to do with this, just mentioning it.

[Eivind Lysne (eivindlysne)]

This problem likely originates in the backend, between nav and graphite.

The netmap frontend has a known bug which may cause 1 or 2 links with multiple edges not to display traffic data, but not affect the whole graph.

This behavior is being looked into.

[Peter Gervai (grin)]

It is definitely graphite+timeout related: I see nav is pulling loads of graphite data then stops (without having traffic to show) the same time, no errors logged.

However if I reload immediately graphite pulls the data from cache (I guess) and the traffic shows, almost always. I am pretty sure a 20 second timeout is triggered.

[Peter Gervai (grin)]

By the way the two errors in the opening post are in d3 and jquery, respectively. They should be fixed upstream (and indeed they should).

[Peter Gervai (grin)]

It seems there's plenty places to timeout (like in d3), this should better take care of them all. Right now it works for me even when fetch is 40+ seconds. Well, a spinner would be nice... ;-)

[Morten Brekkevold (mbrekkevold)]

Re-assigning this to John-Magne, since Eivind is no longer on the team...

[John-Magne Bredal (john-m-bredal)]

There is a spinner, but that's for the graph, not the traffic data. Hm.

However, I have added the content of the patches to the bugfix branch. I also rewrote the backend to do a big request for all edges instead of one request per edge. This should theoretically increase speed when fetching the traffic, although I see little improvement for small datasets.

[John-Magne Bredal (john-m-bredal)]

I forgot to say thanks for the patches =) Thanks!

[John-Magne Bredal (john-m-bredal)]

I noticed that every fifth minute netmap did not display interface traffic. This corresponds with the whisper file retentions.

My guess is that the way we calculate the traffic on interfaces (we are dependent on two datapoints to get a value), lead to no data at seemingly random but actually every five minute interval.

I have upped the interval we ask for data for to 15 minutes, which should fix this problem.

[John-Magne Bredal (john-m-bredal)]

I also added two indicators, one for loading the graph data, and one for loading the traffic. This should make it clear if the user is waiting for something.

[John-Magne Bredal (john-m-bredal)]

Fixes here:

https://nav.uninett.no/hg/stable/rev/a1866323be2c
https://nav.uninett.no/hg/stable/rev/a3f3d70302fc
https://nav.uninett.no/hg/stable/rev/50b991e40771