Agent monitors are service monitors that require an agent=
to be installed on the monitored system. An agent is software that collect=
s performance information from the system and transmits that information to=
the Monitoring Station. Using the information gathered by an agent, Uptime=
Infrastructure Monitor can alert users to changes in an environment based =
on defined thresholds.
File and Directory=
The File and Directory monitor can report the fo=
llowing Directory information:
- Number of files matching a certain regular expression
- Largest file size that matches that expression
- Age (in minutes) of the most recent file
- Most recent date of the latest file
- More recent time of the latest file
- File name that was most recently modified
Configuring File Directory Monitor
Windows
- Download the agent ZIP files.
- Place the filedircheck-win-agent.vbs file in the Uptim=
e agent directory in a subdirectory called "scripts". (
C:\Program =
Files\Uptime Software\Uptime agent\scripts
). Create the scripts dire=
ctory, if needed.
- Run as administrator, the Uptime Agent Console (Start > Upti=
me Agent Console).
- Click Advanced > Custom Scripts.
- Set up a command like this:
Command Name: filedircheck
=
Path to Script: cscript //nologo "C:\Program Files\Uptime Softwar=
e\Uptime agent\scripts\filedircheck-win-agent.vbs"
POSIX
- Place the needed filedircheck-nix-agent.pl file in the=
directory
/opt/uptime-agent/scripts
. Create the scripts direc=
tory, if needed.
- Create/edit the following password file:
/opt/uptime-agent/b=
in/.uptmpasswd
and add the following line to it: fil=
edircheck /opt/uptime-agent/scripts/filedircheck-nix-agent.pl
- Run the following commands to change ownership and permission on
=
/opt/uptime-agent/scripts/filedircheck-nix-agent.pl
chown uptimeagent:uptimeagent /opt/uptime-agent/scripts/filedircheck-nix-a=
gent.plchmod 770 /opt/uptime-agent/sctips/filedircheck-nix-agent.pl
File System =
Capacity
The File System Capacity monitor checks the amount of available=
space on a host's file system, and then compares the data to configured wa=
rning and critical thresholds. Thresholds can be based on percent free or u=
sed, or space free or used (in Megabytes, Gigabytes, or Terabytes).
By default, the service monitor uses global thresholds, which it applies=
to all local drives on Windows systems, or all local file systems on UNIX =
and Linux systems (for example, /var
, /export
, /usr). However, you can fine-tune how file systems are monitored=
using the following options:
- Use regular expressions to exclude one or more file systems from the li=
st of default file systems.
- Use regular expressions to create special cases where the global thresh=
olds are replaced with custom thresholds on one or more mount points.
- Exclude all file systems from capacity monitoring except for those loca=
tions listed as special cases.
- Disable global thresholds and alert on those defined for each special c=
ase.
- Use a combination of exclusions and special cases to augment the list o=
f default file systems.
When using combinations to fine-tune file system monitoring, note that e=
xclusions override the default file systems, and special cases override the=
default file systems and exclusions: if the same file system is added as a=
special case, and also matches a pattern to be excluded, it is still monit=
ored for capacity.
Configuring File System Capacity Monitor
Whether you want to set up a basic capacity monitor or create specific u=
sage thresholds for 100 file systems, use the following common steps:
- Complete the monitor information fields.
To learn how to configure monitor information fields, see M=
onitor Identification.
- Specify values for the Warning and Critical =
Response Time thresholds.
For more information, see Response Time.
To save the data from the thresholds for graphing or reporting, click the =
Save for Graphing checkbox.
- Complete the following settings:
- Configure the options in the File System Capacity Settings section. Refer to the section that applies.
To set a common file system capacity check on local fil=
e systems, do the following:
- In the Global Settings section, complete the following=
fields:=20
- Global Warning Threshold
Create a threshold that generates a warning. This threshold can be an actu=
al amount (in MB, GB, or TB), or percentage of disk space that is used or i=
s free.
- Global Critical Threshold
Create a threshold that generates a critical alert, whether it is an actua=
l amount, or percentage of disk space used or free.
- Ensure the Exclude None option is selected.
Using this option ensures global thresholds are used in conjunction with s=
pecial cases.
- Click Finish.
To create one or more exclusions from a=
common capacity check on local file systems, do the following:
- In the Global Settings section, complete the following=
fields:=20
- Global Warning Threshold
Create a threshold that generates a warning. This threshold can be an actu=
al amount (in MB, GB, or TB), or percentage of disk space that is used or i=
s free.
- Global Critical Threshold
Create a threshold that generates a critical alert, whether it is an actua=
l amount, or percentage of disk space used or free.
-
Select the Exclude File Systems Matching these Patterns op=
tion.
-
In the New Pattern box, use a regular expression to exclude specific mount =
points on the disk from the capacity calculations.
For example, enter D:
(for Windows) or /usr
(for =
Linux or UNIX) to ignore that drive or directory. Enter ^/u.*
=
to ignore all mount points that begin with /u
.
- Click the :plus: icon to add the regular expression to the Sele=
cted Patterns list.
- Optionally continue to add patterns until all file system exclusions ar=
e accounted for.
- Click Finish.
To create custom threshold speci=
al cases for a common capacity check on local file systems, do the followin=
g:
- In the Global Settings section, complete the following=
fields:=20
- Global Warning Threshold
Create a threshold that generates a warning. This threshold can be an actu=
al amount (in MB, GB, or TB), or percentage of disk space that is used or i=
s free.
- Global Critical Threshold
Create a threshold that generates a critical alert, whether it is an actua=
l amount, or percentage of disk space used or free.
- Ensure the Exclude None option is selected.
Using this option ensures global thresholds are used in conjunction with s=
pecial cases.
- For Special Case File Systems, indicate mount points a=
mong the local file systems, then create custom thresholds for them:
- Use a regular expression to indicate the Mou=
nt Point among the local file systems.
- Create a Warning Level threshold fo=
r a Warning Type: a percentage or amount of space used or =
free on the mount point that, when exceeded, generates a warning.
- Create a Critical Level threshold f=
or a Critical Type: a percentage or actual amount of space=
used or free on the mount point that, when exceeded, generates a critical =
alert.
Any thresholds defined as special cases replace any Global Set=
tings thresholds, should they apply.
- Optionally click the :plus: icon to add mount points until all file sys=
tems you wish to add are accounted for.
- Click Finish.
To monitor only specific file systems for capacity, do the follow=
ing:
- Select the Exclude All Except Special Cases option.
Using this option ignores the default list of local file systems from capa=
city monitoring.
- For Special Case File Systems, include specific mount =
points you would like to monitor:=20
- Use a regular expression to indicate the Mount Point among the local fi=
le systems.
- Create a Warning Level threshold for a Warning=
Type: a percentage or amount of space used or free on the mount p=
oint that, when exceeded, generates a warning.
- Create a Critical Level threshold for a Critic=
al Type: a percentage or actual amount of space used or free on th=
e mount point that, when exceeded, generates a critical alert.
- Optionally click the :plus: icon to add mount points until all file sys=
tems you wish to add are accounted for.
- Click Finish.
To monitor local file systems for capac=
ity with some exceptions and special cases, do the following:
- In the Global Settings section, complete the following=
fields:=20
- Global Warning Threshold
Create a threshold that generates a warning. This threshold can be an actu=
al amount (in MB, GB, or TB), or percentage of disk space that is used or i=
s free.
- Global Critical Threshold
Create a threshold that generates a critical alert, whether it is an actua=
l amount, or percentage of disk space used or free.
-
Select the Exclude File Systems Matching these Patterns op=
tion.
-
In the New Pattern box, use a regular expression to exclud=
e specific mount points on the disk from the capacity calculations.
For example, enter D:
(for Windows) or /usr
(for =
Linux or UNIX) to ignore that drive or directory. Enter ^/u.*
=
to ignore all mount points that begin with /u
.
- Click the :plus: icon to add the regular expression to the Sele=
cted Patterns list.
- Optionally continue to add patterns until all file system exclusions ar=
e accounted for.
- For Special Case File Systems, indicate mount points a=
mong the local file systems, then create custom thresholds for them:
- Use a regular expression to indicate the Mount Point=
among the local file systems.
- Create a Warning Level threshold fo=
r a Warning Type: a percentage or amount of space used or =
free on the mount point that, when exceeded, generates a warning.
- Create a Critical Level threshold f=
or a Critical Type: a percentage or actual amount of space=
used or free on the mount point that, when exceeded, generates a critical =
alert.
Any thresholds defined as special cases replace any Global Set=
tings thresholds, should they apply.
- Optionally click the :plus: icon to add mount points until all file sys=
tems you wish to add are accounted for.
- Click Finish.
Process Count=
Check
The Process Count Check monitor measures the number of id=
entical processes that are running on a system. If there is more than one i=
nstance of a process running, the check returns an OK status. If the proces=
s is not running, the check returns a Critical status.
Configuring Process Count Check Monitors
- In the Process Count Check monitor template, complet=
e the monitor information fields.
To learn how to configure monitor information fields, see M=
onitor Identification.
- Complete the following fields:
- Process Name (Mandatory)
The exact name of the process that you want to monitor.
The name is the absolute name of the process, without its path, file exten=
sion, or any parameters.
For example, on UNIX systems, the process " /usr/bi=
n/vmstat -p " is checked as " vmstat ", an=
d on Windows systems, " process.exe " should be=
entered as " process ".
- Process Occurrences
Enter the number of process occurrences for which you want to set Warning =
and Critical thresholds. For more information, see Configuring Warning and Critical Thresholds.
- Response Time
Enter the Warning and Critical Response Time thresholds. For more informat=
ion, see Configuring Warning and Critical =
Thresholds.
- To save the data from the thresholds for graphing or=
reporting, click the Save for Graphing checkbox beside ea=
ch of the metrics that you selected in step 3.
- Complete the following settings:
- Click Finish.