Hi Morten
Thank you for your reply.
Den 1. mar. 2018 kl. 08.55 skrev Morten Brekkevold morten.brekkevold@uninett.no:
On Thu, 1 Mar 2018 08:16:49 +0100 soren@fab-it.dk wrote:
"No data was found for the given timeframe. This may indicate a problem with the data collection and/or presentation. Try choosing a longer timeframe to see when the problem started."
But I do get graphs if I choose the "CPU highest average" - so SNMP apparently is working fine.
When I access Graphite directly on port 8000 and traverse the tree Metrics-> nav-> devices-> ip-> port-> ifinOctets I am able to see a graph for that interface.
But are you able to browse the graphs for individual interfaces using NAV? How about the system/cpu graphs for individual devices?
When I access /ipdevinfo/x.x.x.x/#!ports aka the “ports” tab I am able to see the correct link state, vlan, speed and last used. The next tab /ipdevinfo/x.x.x.x/#!portmetrics shows no graph data in any combination of date/packet type. Just to add to the fun - no matter what timeframe I choose, it only shows the last 24 hours. That also goes for the next tab /ipdevinfo/x.x.x.x/#!sysmetrics
From what you're saying, it sounds like your problem is only with the ranked statistics tool itself, not with data collection.
It appears to me that Nav correctly collect the data, but fails to display it via Nav. Nav can access the switches via SNMP, Nav can display CPU load - although only for the last 24 hours. In the /ipdevinfo/?query=x.x.x.x&submit=Search I can the correct data for the switch in the device info tab, and “status” in the right corner is all green - except ip2mac which is yellow and according to the mouse-over is overdue.
I'm curious as to whether this is the message displayed by Ranked statistics if the Graphite request times out before producing a response (I'm not sure).
It might be - I started Apache with no virtual host listening on port 8000 and Nav responds with the expected "internal error”-page. But then of course this blocks all communication going to graphite - so probably not a valid test.
Ranked statistics offloads all its work to graphite-web, but while graphite has an excellent query language for producing this kind of ranked data and/or graphs, it is sadly not very performant. If you have 10.000 interfaces, it needs to chew through the data of 10.000 whisper files, and since there is no indexing, it's going to take a long time. Sometimes, so much that something will eventually time out while waiting for a response from the graphite-web backend.
I’m testing on 2 switches, the second switch was only added due to the missing graphs to rule out incompatibility. I have a total of 107 ports combined on two 24 port switches.
Kind regards from Copenhagen /Søren Aurehøj - Fab:IT