Is this a custom script or one of Hobbit's OOB (out of the box) monitors? If it's custom, you either have to parse the data yourself to generate the RRDs or set up an NCV to handle it for you.
=G=
From: Matthew Tice [mailto:mjtice at gmail.com] Sent: Tuesday, April 01, 2008 1:09 PM To: hobbit at hswn.dk Subject: [hobbit] What happens to client data after handoff?
I'm trying to trace why my rrd file isn't being created. Maybe it has something to do with the output of my script? If I run the following command it shows the transmission is successful.
root at tice:/home/hobbit# /home/hobbit/client/bin/bb --debug 127.0.0.1<http://127.0.0.1> "data tice.blocked cat /blocks.txt"
2008-04-01 11:07:18 Transport setup is:
2008-04-01 11:07:18 bbdportnumber = 1984
2008-04-01 11:07:18 bbdispproxyhost = NONE
2008-04-01 11:07:18 bbdispproxyport = 0
2008-04-01 11:07:18 Recipient listed as '127.0.0.1<http://127.0.0.1>'
2008-04-01 11:07:18 Standard BB protocol on port 1984
2008-04-01 11:07:18 Will connect to address 127.0.0.1<http://127.0.0.1> port 1984
2008-04-01 11:07:18 Connect status is 0
2008-04-01 11:07:18 Sent 38 bytes
2008-04-01 11:07:18 Closing connection
If I look into the hobbit logs it's not showing anything useful (in fact, the logs aren't even updated after the command is run).
So my question is, after the transmission of the data to the server, what happens? Also, there is plenty of documentation out there on how to format a custom STATUS message, but I can't find anything for a custom DATA message (e.g. do I leave the $COLOR in the command, etc.?). How should DATA messages be configured?
Any help would be appreciated.
Matt