[Xymon] Serial alarm feeds

[Kevin King]

Ok I got it to post!.... now for the reason, or what I did to make it work.

 

Jeremy, I was using your example of hostname.eagle eagle,  that was the
problem. I changed it to sunos and it posted fine. I did make an entry in
local config for eagle and it would build the config file correctly so I
thought I was good to go.

Looks like some deeper work is needed to support custom clients.  

With this I might go back and try your first script suggestion to see if it
will work with sunos replacing eagle..

 

Wait I have a very dim light bulb flashing above my head.. the host I am
running this on is sun, so maybe somewhere it is checking a uname -a that I
overlooked.  So it might be a local issue, see I came back to that. J

 

This was fun and I can see this working with your xymon remote client to
process the log files.  

 

 

 

Now to dig a bit deeper to see what has to be done to create an eagle
hostclass and ostype

 

-Kevin

 

 

From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] 
Sent: Thursday, August 29, 2013 12:37 AM
To: KING, KEVIN
Cc: Kevin King; xymon at xymon.com
Subject: Re: [Xymon] Serial alarm feeds

 

On 29 August 2013 10:24, KING, KEVIN <KK1051 at att.com> wrote:

Ok made some progress today. I am getting a formatted client message, just
not getting it to post.  It may have something to do with it being local.

 

Nope, that should not be a problem.  Xymon doesn't normally care where a
client message comes from as long as the hostname matches an entry in
hosts.cfg.

 

Anyway I do not have anything showing  up in ghost clients and have not
found anything in any logs barking about this.

 

Strange.

 

  But this is looking very promising. I am sure tomorrow will bring more
advances. Your perspective has been very helpful Jeremy.

 

Happy to help.

 

I'd be running the xymond_channel process to see if it catches the client
messages you're sending, and perhaps compare with other client messages.
Something like this:


$ xymoncmd xymond_channel --filter="lkmrflmf00w" --channel=client cat 

 

This will capture client messages where the first line contains
"lkmrflmf00w".  You can replace "cat" with "grep" or "sed" or other commands
that limit the output.  Although if this is the only message for this host
then probably not necessary in this case.

 

J

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20130829/b7d9f40b/attachment.html>