ServersApache::VMonitor -- The Visual System and Apache Server Monitor Page 4

Apache::VMonitor — The Visual System and Apache Server Monitor Page 4




Now you need to specify which processes are to be monitored. The
regular expression that will match the desired processes is required
for this section to work. For example if you want to see all the
processes whose name include any of these strings: http, mysql
and squid, the following regular expression is to be used:

  ::VMonitor::PROC_REGEX = join "|", qw(httpd mysql squid);

mount(1) Emulation

This section reports about mounted filesystems, the same way as if you
have called mount(1) with no parameters.

If you want the mount(1) section to be displayed set:

  ::VMonitor::Config{MOUNT} = 1;

The default is NOT to display this section.

df(1) Emulation

This section completely reproduces the df(1) utility. For each mounted
filesystem it reports the number of total and available blocks (for
both superuser and user), and usage in percents.

In addition it reports about available and used file inodes in numbers
and percents.

This section has a capability of visual alert which is being triggered
when either some filesystem becomes more than 90% full or there are
less than 10% of free file inodes left. When this event happens the
filesystem related report row will be displayed in the bold font and
in the red color. A mount point directory will blink if the blinking
is turned on. You can turn the blinking on with:

  ::VMonitor::Config{BLINKING} = 1;

If you don’t want the df(1) section to be displayed set:

  ::VMonitor::Config{FS_USAGE} = 0;

The default is to display this section.

for more than 90% and therefore colored in red. (It’s normal for
/mnt/cdrom, which is a mounted cdrom, but critical for the /usr
filesystem which should be cleaned up or enlarged).

abbreviations and hints

The report uses many abbreviations, which might be knew for you. If
you enable the VERBOSE mode with:


  ::VMonitor::Config{VERBOSE} = 1;

this section will reveal all the full names of the abbreviations at
the bottom of the report.

The default is NOT to display this section.

A Single Process Extensive Reporting System

If you need to get an in-depth information about a single process, you
just need to click on its PID.

If the chosen process is a mod_perl process, the following info is
displayed:

  • Process type (child or parent), status of the process (Starting,
    Reading, Sending, Waiting, etc.), how long the current
    request is processed or the last one was processed if the process is
    inactive at the moment of the report take.

  • How many bytes transferred so far. How many requests served per child
    and per slot.

  • CPU times used by process: total, utime, stime, cutime,
    cstime.

For all (mod_perl and non-mod_perl) processes the following
information is reported:

  • General process info: UID, GID, State, TTY, Command line arguments

  • Memory Usage: Size, Share, VSize, RSS

  • Memory Segments Usage: text, shared lib, date and stack.

  • Memory Maps: start-end, offset, device_major:device_minor, inode,
    perm, library path.

  • Loaded libraries sizes.

Latest Posts

Related Stories