So, as far is it being purple it was doing exactly what I told it to do. D'oh. I've changed the tag to status and it's turned green, however, I'm very doubtful that it continue to correctly return the status of the test. I'll see if I can get the log entries from the next time it goes yellow for unreturned status.
Thanks,
Jamison Maxwell
user-87d336c3dce6@xymon.invalid<mailto:user-87d336c3dce6@xymon.invalid>
From: Jeremy Laidman [user-71895fb2e44c@xymon.invalid]
Sent: Wednesday, November 06, 2013 6:27 PM
To: Jamison Maxwell
Cc: xymon at xymon.com
Subject: Re: [Xymon] Xymon NetApp.pl Fails to load CPU Data
Yes, it's sending a data message with the word "green" in it. A "data" message doesn't update the status/colour of a column, which would explain why you're getting a purple. Only a "status" message can update the colour of a column.
J
On 7 November 2013 04:24, Jamison Maxwell <user-87d336c3dce6@xymon.invalid<mailto:user-87d336c3dce6@xymon.invalid>> wrote:
I've been running netapp.pl<http://netapp.pl>; for the last couple of months, but all of the sudden I've had nothing but trouble with the CPU test. At first, it was failing to retrieve CPU data and turning yellow with no real explanation that I could find for why it was failing. Now, I've added the data tag to the bbcpucolumn in netapp.ini and it's staying purple. This would make sense if it was actually failing to return the data, however, it appears that it is in fact retrieving it correctly. I get these two log entries when I grep for cpu:
Wed Nov 6 11:05:06 2013:DEBUG: TEST=cpu, TYPE=data, EVENT=cpu, SENDTYPE=2, TESTLIVE=Server Default, SUMREPTIME=0
Wed Nov 6 11:05:06 2013:DEBUG: BBDISPLAY: $XYMONSERVER, hostname: $FILERNAME, type: data, event: cpu, time: 00:00:01, color=green
Now, to my untrained eyes it appears that it's trying to send a green status to Xymon, which is further backed up by having no holes in my RRD graph. I would really appreciate any suggestions for how to proceed as I am at a loss.
Jamison Maxwell
user-87d336c3dce6@xymon.invalid<mailto:user-87d336c3dce6@xymon.invalid>