serverside tests using data from multiple clients?
list Elizabeth Schwartz
Here's our situation. We've got some things we want to watch multiple servers, that will come through as a name-value pair (once we write the local test) So on server one I might have foo-23 bar-25 and on server two I might have bar- 17 baz 3 We want to to do some tests that would involve adding and correlating all this information. There can be *many* possible names, not just three What's the most xymon-like way to do it? Can I send data through client tests that is *read* by server-side tests ? (I vaguely remember there was a way to do it but searching is not workign for me today). One way to do it is to make a log file for each client, rsync the logs to a common location , and then run a single custom test on that location, but that strikes me as beign a bit "outside the box". I want to work within xymon whenever possible, and having individual client tests and the combo test accessible from the xymon interface would b e nice. thanks for any thoughts or clues
list Vernon Everett
We had something similar at a previous client.
I am assuming that these measures are all related, and you want to see them
all in one place?
"Invent" a dummy server. Let's call it dserv1
Remember, when you send data from a client, the client name is in the data
message.
If all of these tests send their data with $MACHINE is set to dserv1, it
really doesn't matter where the data comes from, the Xymon server will
think it's data from dserv1, and treat it as such.
Now you have all the data in one place, making consolidation relatively
trivial.
Regards
Vernon
▸
On 23 November 2011 08:13, Elizabeth Schwartz <user-c61747246f66@xymon.invalid>wrote:
Here's our situation. We've got some things we want to watch multiple servers, that will come through as a name-value pair (once we write the local test) So on server one I might have foo-23 bar-25 and on server two I might have bar- 17 baz 3 We want to to do some tests that would involve adding and correlating all this information. There can be *many* possible names, not just three What's the most xymon-like way to do it? Can I send data through client tests that is *read* by server-side tests ? (I vaguely remember there was a way to do it but searching is not workign for me today). One way to do it is to make a log file for each client, rsync the logs to a common location , and then run a single custom test on that location, but that strikes me as beign a bit "outside the box". I want to work within xymon whenever possible, and having individual client tests and the combo test accessible from the xymon interface would b e nice. thanks for any thoughts or clues
--
"While it is futile to try to eliminate risk, and questionable to try to
minimize it, it is essential that the risks taken be the right risks. "
- Peter F. Drucker
list David Baldwin
Betsy,
▸
Here's our situation. We've got some things we want to watch multiple servers, that will come through as a name-value pair (once we write the local test) So on server one I might have foo-23 bar-25 and on server two I might have bar- 17 baz 3 We want to to do some tests that would involve adding and correlating all this information. There can be *many* possible names, not just three What's the most xymon-like way to do it? Can I send data through client tests that is *read* by server-side tests ? (I vaguely remember there was a way to do it but searching is not workign for me today). One way to do it is to make a log file for each client, rsync the logs to a common location , and then run a single custom test on that location, but that strikes me as beign a bit "outside the box". I want to work within xymon whenever possible, and having individual client tests and the combo test accessible from the xymon interface would b e nice. thanks for any thoughts or clues
A couple of options you could try: * send a 'data' message with you blob of data against a particular test name - doesn't generate a column as such, but gives a way of sending in data. You then need a listener on the data channel to intercept and process the received data. * hack the client and add a separate section into the client report, then put a listener on the client channel to handle that sections data. Something like http://xymonton.org/monitors:check-client David. -- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 user-cbbf693f2c89@xymon.invalid Leverrier Street Bruce ACT 2617 Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.