I'm afraid the Grafana community won't be able to help, it has to be related to the data.
Can you share another screenshot of a cluster that displays data in "All", but nothing when selected ?
... View more
Hello G,
The upgrade of Harvest is pretty safe for existing data.
First of all, regarding the actual performance data, this all happens in Graphite,a nd Harvest isn't touching, except to add new metrics, so a Harvest upgrade will never remove performance and capacity data.
Regarding your dashboards, you might have noticed that Harvest dahboards have special tags on it :
Only dashboards having these tags will be deleted and replaced (again, without touching the actual data), so if you have any dashboards of your own without these tags, they are safe as well.
Hope this helps.
... View more
I don’t anticipate any issue either. Especially if you’re not reinstalling the appliance. And even then you shouldn’t have any issue. Just ping me if you do.
... View more
Interesting.
Are you sure that NAbox can communicate with OCUM over port 443 ?
If the answer is yes, any time I had a similar issue it was solved by an OCUM reboot...
... View more
You probably didn't configure OCUM poller. For capacity information, you need to have OCUM installed and configure it in NAbox.
If you just configure your cluster you will only get performance metrics.
... View more
Grafana, or NetApp Harvest actually, is a community supported product, and though the community is usually very active, you cannot rely on NetApp support for your monitoring.
Also, Grafana lacks the alerting features OPM comes with, and has no analysis engine to forecast performance and alert on deviations, this is a nice feature in OPM.
Use Harvest for more advanced troubleshooting when people have the skills to read the different metrics, but I suggest that you always install NetApp tools for basic monitoring features.
... View more
These requirements are actually described in the Harvest Install and Admin Guide that you can find while downloading Harvest from the Tool Chest. Role operator is good enough for Harvest.
... View more
It's probably an apache server configuration issue.
My config file, for example, locks the listen directive 127.0.0.1
Listen 127.0.0.1:81
Because in effect, I have a rveerse proxy that redirects /graphite to this port internally.
If you share your complete configuration file I will probably be able to figure out why you get connection refused.
... View more
You're talking to the wrong process.
metrics go to port 2003, not 81. 81 is just for querying the metrics and display graphite web interface.
It should be :
echo "blah.metric 50 `date +%s`" | nc 127.0.0.1 2003
... View more
I think you made a mistake in the configuration for Harvest.
You put http://servername and this is incorrect, you should just put servername (or 127.0.0.1).
Port 2003 talking to carbon doesn't use HTTP by the way.
As far as I remember, nc should return to the terminal once the line has been sent, it seems a bit weird to me, but if the folder is created, then it's a good sign, it should work find once you fix Harvest configuration.
Port 81 is probably a different issue. Here is how I configure graphite in NAbox :
# Default configuration file for NAbox/Graphite
Listen 127.0.0.1:81
<IfModule !wsgi_module.c>
LoadModule wsgi_module modules/mod_wsgi.so
</IfModule>
# Read http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGISocketPrefix
WSGISocketPrefix /var/run/apache2/wsgi
<VirtualHost 127.0.0.1:81>
Header set Access-Control-Allow-Origin "*"
Header set Access-Control-Allow-Methods "GET, OPTIONS"
Header set Access-Control-Allow-Headers "origin, authorization, accept"
ServerName graphite
DocumentRoot "/opt/graphite/webapp"
ErrorLog /opt/graphite/storage/log/webapp/error.log
CustomLog /opt/graphite/storage/log/webapp/access.log common
# I've found that an equal number of processes & threads tends
# to show the best performance for Graphite (ymmv).
WSGIDaemonProcess graphite processes=5 threads=5 display-name='%{GROUP}' inactivity-timeout=120
WSGIProcessGroup graphite
WSGIApplicationGroup %{GLOBAL}
WSGIImportScript /opt/graphite/conf/graphite.wsgi process-group=graphite application-group=%{GLOBAL}
# XXX You will need to create this file! There is a graphite.wsgi.example
# file in this directory that you can safely use, just copy it to graphite.wgsi
WSGIScriptAlias / /opt/graphite/conf/graphite.wsgi
Alias /content/ /opt/graphite/webapp/content/
Alias /graphite/static/ /opt/graphite/static/
<Location "/content/">
SetHandler None
</Location>
# XXX In order for the django admin site media to work you
# must change @DJANGO_ROOT@ to be the path to your django
# installation, which is probably something like:
# /usr/lib/python2.6/site-packages/django
Alias /media/ "@DJANGO_ROOT@/contrib/admin/media/"
<Location "/media/">
SetHandler None
</Location>
# The graphite.wsgi file has to be accessible by apache. It won't
# be visible to clients because of the DocumentRoot though.
<Directory /opt/graphite/>
Require all granted
Order deny,allow
Allow from all
</Directory>
</VirtualHost>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
... View more
It could be a bug indeed.
If you switch to mb_per_sec it should be fine.
You can also patch netapp-worker and add on line 2606 :
return ($val * 0.000003814697266) if ($connection{normalized_xfer} eq 'gb_per_sec');
... View more
Hi Raphael,
I looked at Harvest code and this message shouldn't happen, as "wafl_block" is a unit that should be taken care of.
Do you have "normalized_xfer" parameter in the harvest config file?
Are you absolutely sure this isn't an old version of Harvest?
... View more
That's indeed a known bug with a specific version of carbon.
For some reason it seems sometimes NAbox updates itself when it's connected to internet.
I would try re-applying the most recent 2.5b update available on https://nabox.org/downloads/
Le me know how it goes
... View more
Hi Ogi,
There is a problem with the packaging of NetApp Harvest 1.4.1 that will be solved soon.
In th emeantime you can unarchive the one you have on a linux machine, make the scripts executable (netapp-worker and netapp-manager) and recompress it, then it'll work.
Thanks!
... View more