Harvest svm lif counters missing

[dpeverley]

Using Netapp harvest 1.3 and getting lots of great stats from Harvest, we are running OnTap 8.3.2 p2

Just noticed from the /var/log/carbon/listener.log that some stats are not getting in there.

Some Lif interface stats are being ingnored as they look to be sending a space through as part of the name.

21/09/2017 14:56:03 :: invalid line (netapp.perf.London.NETAPP-01.svm.cifs-prd01.lif.cifs-prd01-17n1 .recv_data 2.46365865071615e-06 1506005762) received from client 127.0.0.1:60060, ignoring
21/09/2017 14:56:03 :: invalid line (netapp.perf.London.NETAPP-01.svm.cifs-prd01.lif.cifs-prd01-17n1 .sent_data 1.33514404296875e-06 1506005762) received from client 127.0.0.1:60060, ignoring
21/09/2017 14:57:03 :: invalid line (netapp.perf.London.NETAPP-01.svm.cifs-prd01.lif.cifs-prd01-17n1 .recv_data 1.86284383138021e-05 1506005823) received from client 127.0.0.1:60060, ignoring
21/09/2017 14:57:03 :: invalid line (netapp.perf.London.NETAPP-01.svm.cifs-prd01.lif.cifs-prd01-17n1 .sent_data 1.33514404296875e-06 1506005823) received from client 127.0.0.1:60060, ignoring

These perfcounters look to be being collected by harvest but are being skipped going into graphite and I think it is due to the space after lif name and before the countername, there can't be a space in the lif name.

Anyone know how I can fix this?

[madden]

Hi @dpeverley

Actually, I suspect there *is* actually a trailing space on the LIF name.  LIF naming is very flexible and it's quite easy to get special characters when using system manager.  I've seen the long dash autocorrection (thanks MS Office!) before so this is likely another situation you can hit.  Have you checked the name from the CLI using "net int show"? If it's in quotes and has a space in it you could then use "net int rename" to remove the space.  Please update the communities with your experience!

Cheers,

Chris Madden

Solution Architect - 3rd Platform - Systems Engineering NetApp EMEA (and author of Harvest)

Blog: It all begins with data

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!