Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring AIX monitoring tools for graphical output Post 302472059 by bakunin on Tuesday 16th of November 2010 07:00:54 AM
Old 11-16-2010
Probably your simplest option would be to write a small script.

To monitor the processes use the "ps" command, like in the following script sketch:

Code:
while : ; do
     if [ $(ps -fe | grep "<processname>" | wc -l) -le <minimum_nr_plus_1> ] ; then
          show_error "Not all processes seem to run."
     fi
     sleep <nr_of_seconds>
done

To monitor the memory is more tricky: (almost) all otherwise unused memory is used by the OS for caching purposes, so monitoring "free memory" is completely useless - you get constantly "nearly all memory used" as a result, regardless of how much memory is in fact used by applications.


If you are not interested in exact memory consumption, but only in avoiding paging you could monitor the utilization of the paging space(s) by "lsps -a":

Code:
while : ; do
     if [ $(lsps -s | sed '1d;s/^.*\([0-9][0-9]*\)%.*$/\1/') -gt <threshold_value>] ; then
          show_error "Paging space utilization exceeded."
     sleep <nr_of_seconds>
done

Tomcat is an application and could be monitored like any other process (see above)

Monitoring network connectivity is relatively easy, but with a catch: if the network connection goes down the machine has usually no way of advertising this fact. The best solution is to monitor the system from another host, like in the following sketch:

Code:
while : ; do
     if [ $(ping -c1 <host_to_monitor1>; echo $?) -gt 0 ] ; then
          show_error "Cannot reach <host_to_monitor1>"
     fi
     if [ $(ping -c1 <host_to_monitor2>; echo $?) -gt 0 ] ; then
          show_error "Cannot reach <host_to_monitor2>"
     fi
     [ ...]
     sleep <nr_of_seconds>
done

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. IP Networking

Networking Monitoring Tools

Any idea where can I get a freware to monitor the network traffic in my department? The best is this tool can store the log files. Thanks! (5 Replies)
Discussion started by: zheng_soon
5 Replies

2. Infrastructure Monitoring

UNIX Monitoring tools

I need some monitoring tools for SCO 7.1.4 Does anybody reccomend some software that I can install to monitor mem leaks and odd SAR values etc (2 Replies)
Discussion started by: trebor1
2 Replies

3. UNIX for Advanced & Expert Users

UNIX monitoring tools

Guys, I would like to know who are using monitoring tools? I use Nagios before but it seems is more on Linux and Windows platform. - Nagios - BigBrother - BigSister - Cacti - MRTG - JFFNMS - anymore? Please give comment too I would like to have some comment on UNIX monitoring tools.... (2 Replies)
Discussion started by: dwarf007
2 Replies

4. Red Hat

Monitoring tools

Hi, In HPUX there is a grate monitor tools named GLANCE, which give you information on the disks load, memory usage, cpu ... What is the equivalent tool in LINUX Redhat 4. Thanks (3 Replies)
Discussion started by: yoavbe
3 Replies

5. AIX

AIX 4.2 temperature monitoring tools included ?

Are there any AIX 4.2 commands that would give me the ability to monitor the hardware temperature ? I did a forum search and found nothing about AIX. I checked the 'diag' command but it does not say anywhere that it has this feature. I tried the 'prtdiag' command but it does not exist on the... (6 Replies)
Discussion started by: Browser_ice
6 Replies

6. Solaris

Recommend graphical monitoring tool for sun

Hi folks I am looking for tool which have graphical presentation for cpu and disk characteristics. Cpu is the least of the concern, disk is the most. We use san devices and i know which id's correspond to it. But the problem is that at least one of the tool I tried to use - Quest Sportlight does... (6 Replies)
Discussion started by: ggolub
6 Replies

7. Infrastructure Monitoring

Monitoring tools

I am interested whitch tools are the best by monitoring the UNIX processes and network interfaces ? and whitch tools for management UNIX ? I know that the nagios very good monitoring tools, but interested me and others who have ? (4 Replies)
Discussion started by: danyy
4 Replies

8. UNIX for Dummies Questions & Answers

UNIX user monitoring tools

Hello mates.. i need help with these things *Users should be allowed to login only once, i.e Multiple logins from single user should be restricted and should issue an alert if any user tries . *statistics of everyday log in time ,duration of login,and the commands executed by the user *Alert... (6 Replies)
Discussion started by: safijunaid
6 Replies

9. Red Hat

Recommendations on GRAPHICAL Monitoring Tool

Need assistance in finding a Graphical Monitoring tool open source for Centos , REDHAT linux which doesnt require "root" to compile the tool. Tool that does performance monitoring for Disk usage, CPU, Memory ,Network stats Need install and configure steps as well . (2 Replies)
Discussion started by: ajayram_arya
2 Replies

10. AIX

Monitoring tools

The monitoring tools what we have not able to see historical information about the process name or pid number for the process that consumed high CPU or memory or paging space. Can you please suggest some of the best monitoring tools available in the market that monitors primarily AIX and other Unix... (0 Replies)
Discussion started by: baladelaware73
0 Replies
niffconfig(8)						      System Manager's Manual						     niffconfig(8)

NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF) SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...] OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options. Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame- ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout). Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout). DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter- faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command. Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified. EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0 SEE ALSO
Daemons: niffd(8) Information: EVM(5), nifftmt(7) niffconfig(8)
All times are GMT -4. The time now is 12:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy