Couple of questions on client data
This is the info I need but it sounded like I can get it from historical periods, which is what I'm after.
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922 (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `'
On Jan 10, 2016, at 18:56, David Boyer <davieb at gmail.com<mailto:davieb at gmail.com>> wrote:
Ryan, What specific data are you looking for? If it's the kernel version, this could pull the info:
[xymon at xytest bin]$ ./xymon localhost "clientlog yumlist section=uname" [uname] Linux yumlist 2.6.32-504.12.2.el6.x86_64 x86_64
Or more detailed info: [xymon at xytest bin]$ ./xymon localhost "clientlog yumlist section=osversion" [osversion] CentOS 6.6 LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.6 (Final) Release: 6.6 Codename: Final
and grab what you need...
Dave
On Sun, Jan 10, 2016 at 6:31 PM, Novosielski, Ryan <novosirj at ca.rutgers.edu<mailto:novosirj at ca.rutgers.edu>> 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.
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922<tel:973%2F972.0922> (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `'
On Jan 10, 2016, at 06:48, J.C. Cleaver <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> 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.
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...
Click a convenient red/yellow dot, to: https://xymon.com/xymon-cgi/historylog.sh?HOST=claudio.hswn.dk&SERVICE=conn&...
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=145...
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 <davieb at gmail.com<mailto:davieb at gmail.com>> 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 <novosirj at ca.rutgers.edu<mailto:novosirj at ca.rutgers.edu>> 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 <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> 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.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Thanks, must have just missed it before, as that's just what I thought of to do. Or maybe not visible from a phone somehow. Great tip!
-- ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | novosirj at rutgers.edu - 973/972.0922 (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `'
From: J.C. Cleaver [cleaver at terabithia.org] Sent: Sunday, January 10, 2016 9:00 PM To: Novosielski, Ryan Cc: Xymon Mailing List Subject: Re: [Xymon] Couple of questions on client data
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...
Click a convenient red/yellow dot, to: https://xymon.com/xymon-cgi/historylog.sh?HOST=claudio.hswn.dk&SERVICE=conn&...
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=145...
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 <davieb at gmail.com<mailto:davieb at gmail.com>> 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 <novosirj at ca.rutgers.edu<mailto:novosirj at ca.rutgers.edu>> 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 <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> 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.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Ryan,
JC beat me to the reply! Xymon works a bit differently than BigBrother. It only archives the "changes in state" verses keeping iteration by default. So, in one of my ext scripts, I have it go "clear status (blue)" for 1 iteration thereby it now becomes a historial event.
Dave
On Sun, Jan 10, 2016 at 9:00 PM, J.C. Cleaver <cleaver at terabithia.org> wrote:
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...
Click a convenient red/yellow dot, to:
https://xymon.com/xymon-cgi/historylog.sh?HOST=claudio.hswn.dk&SERVICE=conn&...
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=145...
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 <davieb at gmail.com<mailto:davieb at gmail.com>> 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 <novosirj at ca.rutgers.edu<mailto:novosirj at ca.rutgers.edu>> 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 <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> 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.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (3)
-
cleaver＠terabithia.org
-
davieb＠gmail.com
-
novosirj＠ca.rutgers.edu