Xymon Mailing List Archive search

Couple of questions on client data

list Japheth Cleaver
Sun, 10 Jan 2016 18:00:23 -0800
Message-Id: <user-801a32e0a7c0@xymon.invalid>

From a status page:

https://xymon.com/xymon-cgi/svcstatus.sh?HOST=claudio.hswn.dk&SERVICE=conn

Click the History button, to:
https://xymon.com/xymon-cgi/history.sh?HISTFILE=claudio.hswn.dk.conn&ENTRIES=50&IP=192.168.20.1&DISPLAYNAME=claudio.hswn.dk

Click a convenient red/yellow dot, to:
https://xymon.com/xymon-cgi/historylog.sh?HOST=claudio.hswn.dk&SERVICE=conn&TIMEBUF=Mon_Dec_21_22:56:37_2015

Then scroll down and you should see a "Client Data available" link, to:
https://xymon.com/xymon-cgi/historylog.sh?CLIENT=claudio.hswn.dk&TIMEBUF=1450734721

Which should give you what was needed.

If there's *no* Client Data available anywhere on any links, make sure the
[hostdata] section is not disabled in tasks.cfg and that
--store-clientlogs is set properly in the options to xymond (by default,
it's "--store-clientlogs=!msgs"). You should see directories under
$XYMONVAR/hostdata/ by default.

Also, IIRC xymond_hostdata will by default skip storage when there's <5%
disk space free on the server it's running on.


HTH,

-jc


On Sun, January 10, 2016 5:18 pm, Novosielski, Ryan wrote:
This is the info I need but it sounded like I can get it from historical
periods, which is what I'm after.
On Jan 10, 2016, at 18:56, David Boyer
<user-a6c09f28d9d2@xymon.invalid<mailto:user-a6c09f28d9d2@xymon.invalid>> wrote:

Ryan,
     What specific data are you looking for?  If it's the kernel version,
this could pull the info:
On Sun, Jan 10, 2016 at 6:31 PM, Novosielski, Ryan
<user-6e4f7a3bb37f@xymon.invalid<mailto:user-6e4f7a3bb37f@xymon.invalid>> wrote:
Actually: how do you get at this? I can't see a way after hunting around a
bit. I thought maybe in a client data link at the bottom of a historical
page, but none is present.
On Jan 10, 2016, at 06:48, J.C. Cleaver
<user-87556346d4af@xymon.invalid<mailto:user-87556346d4af@xymon.invalid>> wrote:

This becomes even more relevant when you consider snapshoting. When a
status goes "red", a snapshot of the client data at that time is kept. So
if you went back later to try to figure out why (e.g.) CPU was rising,
the
output of the '[who]' section tells you who might have been doing
something then, even if the data wasn't used for making a test out of at
that time.