Xymon Mailing List Archive search

Question concerning port monitoring

11 messages in this thread

list Tom Moore · Thu, 28 Apr 2011 17:29:51 +0000 ·
Greetings,

We have a server that is running 3 different processes.  In the hobbit-clients.cfg file, I have some PORT checks that are making sure they are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I can't just disable the "ports" check, because that will disable the monitors for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able to enable/disable/acknowledge separately?

Thanks,

Tom
list Elizabeth Schwartz · Thu, 28 Apr 2011 14:28:21 -0400 ·
I'd be interested in any answers you receive! I've got almost the same
problem - servers that are switched between one of several porst for
http, and was thinking I'd need to drop the tests into separate
external tests (which would lose the every-30-second retest for http)
but am interested to know if there's a better way.
quoted from Tom Moore

On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

list Tim McCloskey · Thu, 28 Apr 2011 11:47:32 -0700 ·
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.


For example: 

HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....

HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...


Tim
quoted from Tom Moore


On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

list Ryan Novosielski · Thu, 28 Apr 2011 14:49:16 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.
quoted from Tim McCloskey

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.


For example: 

HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....

HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...


Tim


On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

- -- 
- ---- _  _ _  _ ___  _  _  _

|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk25tqwACgkQmb+gadEcsb4tHQCgqAJ12L/lzkp1dPPLO5B1sxGX
NhQAoI6+DfhfkaeIHEwPGBOHJeP/qnAh
=X4k5
-----END PGP SIGNATURE-----
list Tim McCloskey · Thu, 28 Apr 2011 11:54:05 -0700 ·
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.

Thanks, 

Tim
quoted from Ryan Novosielski
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.


For example:

HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....

HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...


Tim


On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk25tqwACgkQmb+gadEcsb4tHQCgqAJ12L/lzkp1dPPLO5B1sxGX
NhQAoI6+DfhfkaeIHEwPGBOHJeP/qnAh
=X4k5
-----END PGP SIGNATURE-----
list Ralph Mitchell · Thu, 28 Apr 2011 18:06:16 -0400 ·
Personally, I think I'd put check scripts on another system and check the
server instances individually, with different report columns for each.  I
had that working really well at EDS, with over 2500 reports being generated
for around 400 different "systems".  The test system was also the Xymon
server, which was a 733MHz, single cpu DL380.  I used cron for scheduling,
mostly every 5 minutes, with some longer periods (e.g. ssl certs once per
day) and one test that ran every 30 seconds...  :)

Ralph Mitchell
quoted from Tim McCloskey


On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that
host so port 5321 is down and it goes red.....  Okay that's a different
issue.  Will have to think about that for a bit.

Thanks,

Tim
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ryan
Novosielski [user-ae4522577e16@xymon.invalid]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for
host xyz and other ports for host abc I can tell the software to do this by
configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).
 These tests could also be for the same ports on different hosts.  Make sure
that the changes appear above the DEFAULT stanza in the file.

For example:

HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow
TEXT=netbackup
....

HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow
TEXT=splat
...


Tim


On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure
they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the
monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being
able
to enable/disable/acknowledge separately?

Thanks,

Tom

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk25tqwACgkQmb+gadEcsb4tHQCgqAJ12L/lzkp1dPPLO5B1sxGX
NhQAoI6+DfhfkaeIHEwPGBOHJeP/qnAh
=X4k5
-----END PGP SIGNATURE-----

list Tim McCloskey · Thu, 28 Apr 2011 15:18:22 -0700 ·
I think you're right on that one.  Unless there are different ip|name:port pairs I don't see how this can be implemented without some scripting.  That's one of the really cool things about xymon -- you can create pretty much whatever you want to extend the system.
733MHz!  Wow, that's some high tech kit.  Most of our servers are 16MHz 8080's with 64k of RAM.
quoted from Ralph Mitchell

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell [user-00a5e44c48c0@xymon.invalid]
Sent: Thursday, April 28, 2011 3:06 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

Personally, I think I'd put check scripts on another system and check the server instances individually, with different report columns for each.  I had that working really well at EDS, with over 2500 reports being generated for around 400 different "systems".  The test system was also the Xymon server, which was a 733MHz, single cpu DL380.  I used cron for scheduling, mostly every 5 minutes, with some longer periods (e.g. ssl certs once per day) and one test that ran every 30 seconds...  :)

Ralph Mitchell


On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid<mailto:user-440820cc07d6@xymon.invalid>> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.

Thanks,

Tim
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Question concerning port monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.


For example:

HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....

HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...


Tim


On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid<mailto:user-09591bca676f@xymon.invalid>> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can’t just disable the “ports” check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer

|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid> - 973/972.0922<tel:973%2F972.0922> (2-0922)
quoted from Ralph Mitchell
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk25tqwACgkQmb+gadEcsb4tHQCgqAJ12L/lzkp1dPPLO5B1sxGX
NhQAoI6+DfhfkaeIHEwPGBOHJeP/qnAh
=X4k5
-----END PGP SIGNATURE-----
list Ryan Novosielski · Fri, 29 Apr 2011 11:25:23 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I normally handle this sort of thing through virtualhosts. If you're not
talking web, though, and don't need to bother with that then maybe it's
a different story.
quoted from Tim McCloskey

On 04/28/2011 06:18 PM, Tim McCloskey wrote:
I think you're right on that one.  Unless there are different ip|name:port pairs I don't see how this can be implemented without some scripting.  That's one of the really cool things about xymon -- you can create pretty much whatever you want to extend the system.
733MHz!  Wow, that's some high tech kit.  Most of our servers are 16MHz 8080's with 64k of RAM.

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell [user-00a5e44c48c0@xymon.invalid]
Sent: Thursday, April 28, 2011 3:06 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

Personally, I think I'd put check scripts on another system and check the server instances individually, with different report columns for each.  I had that working really well at EDS, with over 2500 reports being generated for around 400 different "systems".  The test system was also the Xymon server, which was a 733MHz, single cpu DL380.  I used cron for scheduling, mostly every 5 minutes, with some longer periods (e.g. ssl certs once per day) and one test that ran every 30 seconds...  :)

Ralph Mitchell


On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid<mailto:user-440820cc07d6@xymon.invalid>> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.

Thanks,

Tim
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Question concerning port monitoring

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.
For example:
HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....
HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...
Tim
On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid<mailto:user-09591bca676f@xymon.invalid>> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I

can t just disable the  ports  check, because that will disable the monitors
quoted from Tim McCloskey
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

- -- 
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk262GMACgkQmb+gadEcsb6uCQCgyPGnbTIHbw8E3vGj0uNlouMA
NtcAnA1e6eKSR0QgRuW60hu9AptnwcLs
=v6F6
-----END PGP SIGNATURE-----
list Tim McCloskey · Fri, 29 Apr 2011 09:28:00 -0700 ·
I'd prefer to have dev, test and prod on different IP's but that might not be possible|allowed in Tom's env.
quoted from Ryan Novosielski

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid]
Sent: Friday, April 29, 2011 8:25 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I normally handle this sort of thing through virtualhosts. If you're not
talking web, though, and don't need to bother with that then maybe it's
a different story.

On 04/28/2011 06:18 PM, Tim McCloskey wrote:
I think you're right on that one.  Unless there are different ip|name:port pairs I don't see how this can be implemented without some scripting.  That's one of the really cool things about xymon -- you can create pretty much whatever you want to extend the system.
733MHz!  Wow, that's some high tech kit.  Most of our servers are 16MHz 8080's with 64k of RAM.

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell [user-00a5e44c48c0@xymon.invalid]
Sent: Thursday, April 28, 2011 3:06 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

Personally, I think I'd put check scripts on another system and check the server instances individually, with different report columns for each.  I had that working really well at EDS, with over 2500 reports being generated for around 400 different "systems".  The test system was also the Xymon server, which was a 733MHz, single cpu DL380.  I used cron for scheduling, mostly every 5 minutes, with some longer periods (e.g. ssl certs once per day) and one test that ran every 30 seconds...  :)

Ralph Mitchell


On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid<mailto:user-440820cc07d6@xymon.invalid>> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.

Thanks,

Tim
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Question concerning port monitoring

By server, he means "server instance." If he stops one "server" (like an
instance of Tomcat or something), he would like it to be separated out
from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.
For example:
HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup
....
HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat
...
Tim
On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid<mailto:user-09591bca676f@xymon.invalid>> wrote:
Greetings,

We have a server that is running 3 different processes.  In the
hobbit-clients.cfg file, I have some PORT checks that are making sure they
are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I
can t just disable the 
ports
 check, because that will disable the monitors
for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able
to enable/disable/acknowledge separately?

Thanks,

Tom

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk262GMACgkQmb+gadEcsb6uCQCgyPGnbTIHbw8E3vGj0uNlouMA
NtcAnA1e6eKSR0QgRuW60hu9AptnwcLs
=v6F6
-----END PGP SIGNATURE-----
list Tom Moore · Fri, 29 Apr 2011 22:37:24 +0000 ·
Well yes, that's the plan (to move the environments to separate servers).  But in the meantime.. I would set up virtualhosts.. but while that works fine for server side checks (i.e. websites), I don't think it would work for port status because that information comes from the client and can only match one CLIENT entry server side.
quoted from Tim McCloskey


-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Tim McCloskey
Sent: Friday, April 29, 2011 12:28 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

I'd prefer to have dev, test and prod on different IP's but that might not be possible|allowed in Tom's env.

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid]
Sent: Friday, April 29, 2011 8:25 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I normally handle this sort of thing through virtualhosts. If you're not talking web, though, and don't need to bother with that then maybe it's a different story.

On 04/28/2011 06:18 PM, Tim McCloskey wrote:
I think you're right on that one.  Unless there are different ip|name:port pairs I don't see how this can be implemented without some scripting.  That's one of the really cool things about xymon -- you can create pretty much whatever you want to extend the system.
733MHz!  Wow, that's some high tech kit.  Most of our servers are 16MHz 8080's with 64k of RAM.

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell [user-00a5e44c48c0@xymon.invalid]
Sent: Thursday, April 28, 2011 3:06 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

Personally, I think I'd put check scripts on another system and check the server instances individually, with different report columns for each.  I had that working really well at EDS, with over 2500 reports being generated for around 400 different "systems".  The test system was also the Xymon server, which was a 733MHz, single cpu DL380.  I used cron for scheduling, mostly every 5 minutes, with some longer periods (e.g. ssl certs once per day) and one test that ran every 30 seconds...  :)

Ralph Mitchell


On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid<mailto:user-440820cc07d6@xymon.invalid>> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.

Thanks,

Tim
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Question concerning port monitoring

By server, he means "server instance." If he stops one "server" (like an instance of Tomcat or something), he would like it to be separated out from other instances of same on the same machine.

On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.
For example:
HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup ....
HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat ...
Tim
On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid<mailto:user-09591bca676f@xymon.invalid>> wrote:
Greetings,

We have a server that is running 3 different processes.  In the hobbit-clients.cfg file, I have some PORT checks that are making sure they are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I can t just disable the 
ports
 check, because that 
will disable the monitors for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able to enable/disable/acknowledge separately?

Thanks,

Tom

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk262GMACgkQmb+gadEcsb6uCQCgyPGnbTIHbw8E3vGj0uNlouMA
NtcAnA1e6eKSR0QgRuW60hu9AptnwcLs
=v6F6
-----END PGP SIGNATURE-----
list Ryan Novosielski · Fri, 29 Apr 2011 18:42:22 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You could possibly run multiple clients. I would assume that might work
because the client is the one that sends back its name, and that name
does not have to be the host name. I don't think the client listens,
right (thinking port conflicts).
quoted from Tom Moore

On 04/29/2011 06:37 PM, Tom Moore wrote:
Well yes, that's the plan (to move the environments to separate servers).  But in the meantime.. I would set up virtualhosts.. but while that works fine for server side checks (i.e. websites), I don't think it would work for port status because that information comes from the client and can only match one CLIENT entry server side.


-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Tim McCloskey
Sent: Friday, April 29, 2011 12:28 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

I'd prefer to have dev, test and prod on different IP's but that might not be possible|allowed in Tom's env.

From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid]
Sent: Friday, April 29, 2011 8:25 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring

I normally handle this sort of thing through virtualhosts. If you're not talking web, though, and don't need to bother with that then maybe it's a different story.

On 04/28/2011 06:18 PM, Tim McCloskey wrote:
I think you're right on that one.  Unless there are different ip|name:port pairs I don't see how this can be implemented without some scripting.  That's one of the really cool things about xymon -- you can create pretty much whatever you want to extend the system.
733MHz!  Wow, that's some high tech kit.  Most of our servers are 16MHz 8080's with 64k of RAM.
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Ralph Mitchell [user-00a5e44c48c0@xymon.invalid]
Sent: Thursday, April 28, 2011 3:06 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Question concerning port monitoring
Personally, I think I'd put check scripts on another system and check the server instances individually, with different report columns for each.  I had that working really well at EDS, with over 2500 reports being generated for around 400 different "systems".  The test system was also the Xymon server, which was a 733MHz, single cpu DL380.  I used cron for scheduling, mostly every 5 minutes, with some longer periods (e.g. ssl certs once per day) and one test that ran every 30 seconds...  :)
Ralph Mitchell
On Thu, Apr 28, 2011 at 2:54 PM, Tim McCloskey <user-440820cc07d6@xymon.invalid<mailto:user-440820cc07d6@xymon.invalid>> wrote:
Ah -- I see.  Then the ports column covers all of the listeners on that host so port 5321 is down and it goes red.....  Okay that's a different issue.  Will have to think about that for a bit.
Thanks,
Tim
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of Ryan Novosielski [user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>]
Sent: Thursday, April 28, 2011 11:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Question concerning port monitoring
By server, he means "server instance." If he stops one "server" (like an instance of Tomcat or something), he would like it to be separated out from other instances of same on the same machine.
On 04/28/2011 02:47 PM, Tim McCloskey wrote:
I might be missing your question.  If I want to monitor certain ports for host xyz and other ports for host abc I can tell the software to do this by configuring the server side hobbit-clients.cfg (analysis.cfg in xymon).  These tests could also be for the same ports on different hosts.  Make sure that the changes appear above the DEFAULT stanza in the file.
For example:
HOST=fred
....
PORT LOCAL=%(:13782|:13722|:13724|:13783) STATE=LISTEN MIN=1 COLOR=yellow TEXT=netbackup ....
HOST=jane
...
PORT LOCAL=%(:1372|:1322|:1372|:137) STATE=LISTEN MIN=1 COLOR=yellow TEXT=splat ...
Tim
On Thu, Apr 28, 2011 at 1:29 PM, Tom Moore <user-09591bca676f@xymon.invalid<mailto:user-09591bca676f@xymon.invalid>> wrote:
Greetings,

We have a server that is running 3 different processes.  In the hobbit-clients.cfg file, I have some PORT checks that are making sure they are listening on the appropriate port.

The problem I have is if the DEV server is taken down for maintenance, I can t just disable the 
ports
 check, because that 
will disable the monitors for the PROD and TEST ports.

How can I go about splitting out the port checks for a server and being able to enable/disable/acknowledge separately?

Thanks,

Tom

- -- - ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk27Ps4ACgkQmb+gadEcsb7qswCfSXzLaMEiETosBGIV/HZR+UxB
qCYAn2TxzWm33LhqdxCkGavcgx7aX8MJ
=CxGH
-----END PGP SIGNATURE-----