FreeNote?
It occurred to me that several of us with Mon installations on different networks with different providers could all band together and monitor one another. Traps from failed monitors would go upstream to a central box, a sort of collector for all the spread out Mon installs, maybe to two for redundancy. Rules could be setup to only alert when a threshold is hit, perhaps so that several monitors have to agree that a test failed before it sends out a page/email/whatever. The possibilities for alerting are flexible with Mon, that's just one example. Basically I'm thinking of a "poor man's Keynote", or a "FreeNote" service that members donate a Mon install to in order to join. Lots of details would need to be worked out to implement it, most of which aren't appropriate to actually discuss on a general Mon mailing list. I'm really just curious if people see some potential in my cooky idea. Well, do you? -- Cahn's Axiom: When all else fails, read the instructions. msg00713/pgp0.pgp Description: PGP signature
Re: Storing performance history
Paul Socolow wrote: > I know about rrdmon, but that seem to simply record whether the host was up > or down, It can store per host http/smtp/nntp/ldap/... response times on rrdbases > and it runs with its own scheduler. It is a mon server(s) client, but its scheduling is based on mon server(s) intervals. The last release can store on mysql databases. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06 ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Storing performance history
Although Mon was designed on an up/down model, I was wondering about how well it could be used to track performance on a more granular basis. I'd like to store response times from pings and http requests, and be able to graph them or generate statistics. I know about rrdmon, but that seem to simply record whether the host was up or down, and it runs with its own scheduler. Likewise, tools like Cricket which have http polling included, don't seem to have the sophisitication of Mon when it comes to flexibility of polling configuration or parallel requests or differing intervals. I am thinking that it wouldn't be too hard to have the monitor script write to an RRD database the response time it recorded for the poll, and then have some other software graph/digest the data when I needed it. Has anyone else attempted this, or know of someone who has? Thanks, Paul Socolow ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: monitoring Citrix ICA
On 2 Oct 2002, Roderick Schertler wrote: > On Wed, 2 Oct 2002 17:19:01 +0100, Mark Waterhouse <[EMAIL PROTECTED]> said: > > > > You could also [test whether it accepts a TCP connection] for port 1494 > > but I dont use Citrix so am not able to give you any more information. > > When I telnet to port 1494 on my Citrix servers, it immediately outputs > a banner, so you might try: > > telnet.monitor -p 1494 -l '/^\x7f\x7fICA\x00/' host1 host2 another option might be making a script which calls the icaclient (wfica) itself, telling it to run something and exit. maybe it is able to report failures. ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
monitoring Citrix ICA
On Wed, 2 Oct 2002 17:19:01 +0100, Mark Waterhouse <[EMAIL PROTECTED]> said: > > You could also [test whether it accepts a TCP connection] for port 1494 > but I dont use Citrix so am not able to give you any more information. When I telnet to port 1494 on my Citrix servers, it immediately outputs a banner, so you might try: telnet.monitor -p 1494 -l '/^\x7f\x7fICA\x00/' host1 host2 -- Roderick Schertler [EMAIL PROTECTED] ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Does anyone know how to monitor non-standard services (e.g. Citri x sessions)
Hi Simon You could always use a standard tcp.monitor script monitor tcp.monitor!80 That would just connect to tcp port 80 and disconnects if the port allows a connection. You could also do the same for port 1494 but I dont use Citrix so am not able to give you any more information. Regards Mark -Original Message- From: McKay-Mills, Simon [mailto:[EMAIL PROTECTED]] Sent: 02 October 2002 16:36 To: '[EMAIL PROTECTED]' Subject: Does anyone know how to monitor non-standard services (e.g. Citri x sessions) Hi, I am trying to monitor a Citrix farm and wonder if anyone has come across this before. I know the master browser in the farm listens on port 80, but as it is not a standard HTTP server a GET returns an error message. It also uses port 1494 but I have no idea on how to check what is going on. Has anyone come across this before? Regards Simon ... This electronic message transmission contains information that is deemed confidential or privileged by the sender. The information is intended to be for the use of the individual or entity named as recipient(s) above, only. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by telephone (303-397-8100) or by electronic mail([EMAIL PROTECTED]) immediately. ... ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Does anyone know how to monitor non-standard services (e.g. Citrix sessions)
Hi, I am trying to monitor a Citrix farm and wonder if anyone has come across this before. I know the master browser in the farm listens on port 80, but as it is not a standard HTTP server a GET returns an error message. It also uses port 1494 but I have no idea on how to check what is going on. Has anyone come across this before? Regards Simon ... This electronic message transmission contains information that is deemed confidential or privileged by the sender. The information is intended to be for the use of the individual or entity named as recipient(s) above, only. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by telephone (303-397-8100) or by electronic mail([EMAIL PROTECTED]) immediately. ... ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: Scheduling external outages...
--On Wednesday, October 02, 2002 11:37 AM +0200 Erik Inge Bolsø
<[EMAIL PROTECTED]> wrote:
> Any way we could "schedule downtime" in mon, so that on-call people aren't
> woken up by meeping mobile phones over known outages? Hm, apart from doing
> disable_host and enable_host from homegrown perl scripts in crond/atd,
> that is... that could work.
>
Thats what exclude_period is for. Unfortunately there is a known minor bug
in mon 0.99.2 that prevents exclude_periods from working. The fix is to
make the following change:
Search for exclude_period until you find:
elsif ($var eq "exclude_period" && inPeriod (time, $args) == -1)
{
close (CFG);
return "cf error: malformed exclude_period '$args' (the specified time
period is not valid as per Time::Period::inPeriod), line $line_num";
}
Change that to:
elsif ($var eq "exclude_period")
{
if (inPeriod (time, $args) == -1)
{
close (CFG);
return "cf error: malformed exclude_period '$args' (the specified
time period is not valid as per Time::Period::inPeriod), line $line_num";
}
}
(I removed some of the indentation for clarity.)
Then in your mon.cfg in the relevant service you add:
exclude_period
i.e.
exclude_period wd{1} hr{4} min{0-20}
-David Nolan
Network Software Developer
Computing Services
Carnegie Mellon University
___
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
Scheduling external outages...
Greets. We're a small company. Only running a normal daytime workweek shift, with people on-call after hours and during weekends. We're dependant on quite a few external services working - among other things a few SMS gateways located at external telecom companies. From time to time, these external things are down for scheduled maintenance in the middle of the night. Any way we could "schedule downtime" in mon, so that on-call people aren't woken up by meeping mobile phones over known outages? Hm, apart from doing disable_host and enable_host from homegrown perl scripts in crond/atd, that is... that could work. What do people out there do? *curious* -- Erik I. Bolsø, Triangel Maritech Software AS | Skybert AS Tlf: 712 41 694 Mobil: 915 79 512 ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
