[Xymon] No info status from CL

J.C. Cleaver cleaver at terabithia.org
Wed Aug 12 22:34:50 CEST 2015

"info" unfortunately is not a real status. There's a stub entry for it,
but that's really just something to trick xymongen into displaying a dot
for it. The same goes for the 'trends' column, actually, while the
'clientlog' column is derived from a separate record of whether client
data is present in memory.

In the info and trends cases, the data presented when the svcstatus.sh CGI
is called up (in a normal, dynamic config) is calculated live using data
in xymond's live state and/or the hosts.cfg file.

In recent xymon versions, the "clientlog" status is really just retrieving
the clientlog data under the hood.

Under normal loads, the 'clientlog' command is the easiest way to get this.
Under a normal load, looping through a list shouldn't be much of a
problem. At scale, if you have the RAM, we've found setting up a local
tmpfs partition for recording client data works great more more complex
clientlog queries.

I'd considered adding in a "xymondboard"-esque filter, or a way to pull
multiple clientlogs at once, but there are limits to how efficient the
former could be right now, while there hadn't been much demand for the
latter recently. It's something that could probably be added, however.



On Wed, August 12, 2015 12:51 pm, David Welker wrote:
> Ralph,
> That works for clientlog, good catch, but what about the info status - am
> I
> using the wrong format for xymondlog as well?
> Thanks for the help!
> David
> On Wed, Aug 12, 2015 at 9:10 AM, Ralph Mitchell <ralphmitchell at gmail.com>
> wrote:
>> The man page says the syntax is:
>> clientlog HOSTNAME [section=SECTIONNAME[,SECTIONNAME...]] Retrieves the
>> current raw client message last sent by HOSTNAME. The optional "section"
>> filter is used to select specific sections of the client data.
>> so you should be doing something like:
>>    xymon  localhost  "clientlog myhost.local  section=osversion"
>> Ralph Mitchell
>> On Wed, Aug 12, 2015 at 8:38 AM, David Welker <dewelker at gmail.com>
>> wrote:
>>> Running Xymon v4.3.21 on RHEL 6.4 - unable to get info or clientlog
>>> status data (was hoping to grep the OS field in info and/or the
>>> osversion
>>> field in clientlog).  Other test names work fine.
>>> Attempts w/results:
>>> [xymon at myhost ~]$ /usr/local/xymon/server/bin/xymon
>>> "clientlog myhost.local.info"
>>> [xymon at myhost ~]$ /usr/local/xymon/server/bin/xymon
>>> "clientlog myhost.local.clientlog"
>>> [xymon at myhost ~]$ /usr/local/xymon/server/bin/xymon
>>> "xymondlog myhost.local.info"
>>> [xymon at myhost ~]$ /usr/local/xymon/server/bin/xymon
>>> "xymondlog myhost.local.clientlog"
>>> Am I doing something wrong, or is this not possible?
>>> David

More information about the Xymon mailing list