[prev in list] [next in list] [prev in thread] [next in thread]
List: mon
Subject: Re: tcp.monitor usage
From: Jim Trocki <trockij () transmeta ! com>
Date: 2001-08-08 14:12:35
[Download RAW message or body]
On Wed, 8 Aug 2001, Ryan wrote:
> I can't seem to get the tcp.monitor to work. I am trying port 1443 on
> SERVER. I suspect the syntax of my config is wrong. If anyone could
> shed some light. Thanks.
>
>
> watch SERVER
> service SERVICE
> interval 5m
> monitor tcp.monitor 1443
> alert mail.alert rahenr@EPSIIA.com
> alertevery 10m
from doc/README.monitors
tcp.monitor
-----------
Useful to see if it's possible to connect to a particular port
on a particular server. This is over-simplified, and does not yet
support parsing of the output from these services. Options are
"-p port" to tell which port to check, and a list of hosts.
therefore, your config should look like:
watch SERVER
service SERVICE
interval 5m
monitor tcp.monitor -p 1443
alert mail.alert rahenr@EPSIIA.com
alertevery 10m
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic