Hi Morten

Spot on - it was the carbon-cache storage schema. During installation of Nav, I started Nav - unfortunately before configuring Graphite in accordance with your first link.
Initially I skipped your second link in my search for the error, as I was not seeing gaps but was missing the graphs entirely.

Thank you very much for your help.

For the archives:

I could confirm the problem with whisper-info showing the secondsPerPoint in Archive 0 set at 60, not the expected 300

root@nav:~# whisper-info /var/lib/graphite/whisper/nav/devices/192_168_0_10/ports/24/ifInOctets.wsp
maxRetention: 51840000
xFilesFactor: 0.5
aggregationMethod: last
fileSize: 45568

Archive 0
retention: 604800
secondsPerPoint: 300 <- was wrongly set to 60
points: 2016
size: 24192
offset: 64


To get back to a clean slate i did the following:

** WARNING -- WILL REMOVE ALL GRAPHITE + NAV-DATA **

/etc/init.d/nav stop; /etc/init.d/carbon-cache stop;
/etc/init.d/apache2 stop
rm -rf /var/lib/graphite/whisper/*
rm /var/lib/graphite/graphite.db
python /usr/share/pyshared/graphite/manage.py syncdb
chown _graphite:_graphite /var/lib/graphite/graphite.db
chmod o-r /var/lib/graphite/graphite.db
su - postgres -c 'psql nav -c "truncate device, vlan, netbios
cascade;"'
/etc/init.d/carbon-cache start; /etc/init.d/nav start;
/etc/init.d/apache2 start

Which I found in the nav-users mailing list [1]


[1] http://nav-users.itea.ntnu.narkive.com/wlPupwV8/setting-up-nav-from-scratch-non-ova-graphite-issues



-- 
Med venlig hilsen / Kind regards
Søren Aurehøj

Fab:IT ApS
Flæsketorvet 75
DK-1620 København
Tlf: +45 70 202 407
www.fab-it.dk

Den 2. mar. 2018 kl. 08.40 skrev Morten Brekkevold <morten.brekkevold@uninett.no>:

On Thu, 1 Mar 2018 09:54:53 +0100 Søren Aurehøj <soren@fab-it.dk> wrote:

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

Aha, this sounds like a classic case of not configuring carbon-cache at
all. With carbon-cache's default storage schema, every metric is only
kept for 24 hours, and all metrics are expected to come at 1 minute
intervals - meaning anything coming in at 5 minute intervals will appear
gappy or completely missing.

Please double check with [1] and [2].

[1] https://nav.uninett.no/doc/4.8/intro/install.html#integrating-graphite-with-nav
[2] https://nav.uninett.no/doc/4.8/faq/graph_gaps.html#whisper-files-have-the-wrong-storage-schema

--
Morten Brekkevold
UNINETT