Hello,
I have Xymon 4.3.7 installed in '/home/xymon'. I notice that at the top level there is a directory called 'data' (along with 'acks', 'disabled', 'hist', 'histlogs' etc).
Can someone tell me what the 'data' directory is used for please? It is empty.
On our BB system there is a 'bbvar/data' directory which contains text files of the current status of various tests for hosts. Is there any sort of similar arrangement with Xymon (that is, any ability to store the current reported status in a text file)?
Thanks,
John.
-- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001
On Wed, 2012-04-18 at 16:15 +0100, John Horne wrote:
Hello,
I have Xymon 4.3.7 installed in '/home/xymon'. I notice that at the top level there is a directory called 'data' (along with 'acks', 'disabled', 'hist', 'histlogs' etc).
Actually this is within 'data', so we have '/home/xymon/data/data', '/home/xymon/data/acks' etc.
Can someone tell me what the 'data' directory is used for please? It is empty.
Checking a bit further it seems that this is used by xymon_channel and xymon_filestore.
What I am trying to see is if it is possible for a client to send some information to the server, but have the server simply store the information in a file (ideally one per host per test, similar to found in the 'data/hist' directory). The information will be similar to a status, but will include items which I will have processed later on the server.
I saw mention of 'usermsg' in the xymon(1) man page. Not sure if that could be used... more checking required I think.
John.
-- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001
On Wed, 2012-04-18 at 16:15 +0100, John Horne wrote:
Hello,
I have Xymon 4.3.7 installed in '/home/xymon'. I notice that at the top level there is a directory called 'data' (along with 'acks', 'disabled', 'hist', 'histlogs' etc).
Actually this is within 'data', so we have '/home/xymon/data/data', '/home/xymon/data/acks' etc.
Can someone tell me what the 'data' directory is used for please? It is empty.
Checking a bit further it seems that this is used by xymon_channel and xymon_filestore.
What I am trying to see is if it is possible for a client to send some information to the server, but have the server simply store the information in a file (ideally one per host per test, similar to found in the 'data/hist' directory). The information will be similar to a status, but will include items which I will have processed later on the server.
I saw mention of 'usermsg' in the xymon(1) man page. Not sure if that could be used... more checking required I think.
This does indeed mirror the old BB way of doing things. Check out the [storedata] stanza within tasks.cfg and enable it to start storing "data" messages. "Data" messages don't generate a status column named after their test, and are stored directly on the disk (if storedata is enabled). They also aren't queryable remotely, but anything can subscribe to the "data" channel if you want to process the "data" datastream live.
Asynchronously looping over files in the data/data/ directory and doing something with them works too.
HTH,
-jc
On Wed, 2012-04-18 at 12:18 -0700, cleaver at terabithia.org wrote:
On Wed, 2012-04-18 at 16:15 +0100, John Horne wrote:
I saw mention of 'usermsg' in the xymon(1) man page. Not sure if that could be used... more checking required I think.
This does indeed mirror the old BB way of doing things. Check out the [storedata] stanza within tasks.cfg and enable it to start storing "data" messages. "Data" messages don't generate a status column named after their test, and are stored directly on the disk (if storedata is enabled). They also aren't queryable remotely, but anything can subscribe to the "data" channel if you want to process the "data" datastream live.
Asynchronously looping over files in the data/data/ directory and doing something with them works too.
Hello,
Thanks for this. Do you use channels yourself to do anything like this?
Also I am wondering what the difference is between the 'data' channel and the 'usermsg' channel? If the usermsg channel is 'for whatever the user wants to use it for', then I would prefer using that.
I may be able to get away without actually storing anything if the process on the server-side is fast enough. I'm not sure how the mechanism works, or what happens if a message arrives whilst the process is already processing one. I assume there is some sort of 'wait' mechanism (having said that I think semaphores were mentioned somewhere?).
John.
-- John Horne, Plymouth University, UK Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
On 19-04-2012 20:29, John Horne wrote:
Also I am wondering what the difference is between the 'data' channel and the 'usermsg' channel? If the usermsg channel is 'for whatever the user wants to use it for', then I would prefer using that.
The main difference is that the graph-handling module (xymond_rrd) in the default configuration receives data messages, so if you use a data-message then you must take care to avoid using data-names which are already in use by the standard Xymon tools - and hence recognized by xymond_rrd as something it should parse and build a graph from.
"usermsg" is untouched by the standard Xymon tools, so how that is used is completely up to you.
Regards, Henrik
participants (3)
-
cleaver＠terabithia.org
-
henrik＠hswn.dk
-
john.horne＠plymouth.ac.uk