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 "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'
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 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
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
On Tue, Apr 1, 2008 at 11:22 AM, Galen Johnson <Galen.Johnson at sas.com> wrote:
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.
It's a custom script. I also needed to add it to the test2rrd line in
hobbitserver.cfg. My concern is this, if a custom test isn't doing what it
should it seems it's a lot of guess work trying to figure out what is
happening. I've been setting up custom tests sporadically for over two
years and I still get mixed up. It would be nice if I knew exactly the
chain of operations that is taking place when the server receives a message
from a client e.g. the client runs this command (e.g.
/home/hobbit/client/bin/bb --debug 127.0.0.1 "data tice.blocked cat /blocks.txt") and then the server runs such and such command. That way I
could manually run things to find out where it's failing. If this info is
documented somewhere please point me in the right direction. I'll look
through the man pages but it's easy to get lost in there.
Thanks for the info.
Matt
On Tue, Apr 01, 2008 at 11:09:17AM -0600, Matthew Tice wrote:
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 "data tice.blocked
cat /blocks.txt"
A "data" message is fed to the graph-handling modules (hobbitd_rrd), but nothing else really. So to get a graph from it, you must configure your custom dataset - "blocked" - to go through one of the RRD handles. I.e. either it's in NCV (Name-Colon-Value) format so you must configure the NCV_blocked setting, or it should go to an external script that you tell hobbitd_rrd about on the commandline (in hobbitserver.cfg).
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?
See the bb(1) man-page: data HOSTNAME.DATANAME<newline><additional text>
Regards, Henrik
participants (3)
-
Galen.Johnson＠sas.com
-
henrik＠hswn.dk
-
mjtice＠gmail.com