| Age most recent file (sec) |
| The age of the most recent file when using
wildcards on a file monitor in seconds. If wildcards
are not used, the age of the single specified in
the file
monitor is taken. |
| Usage example: use this criteria if you
need to know that the newest file in a directory
was written
at least an hour ago (3600 seconds) |
| Rule: Age most recent file (sec) - is less than
- 3600 |
| |
| Age oldest file (sec) |
| The age of the oldest file when using a wildcards
on a file monitor in seconds. If wildcards are not
used, the age of the single specified in the file
monitor is taken. |
| Usage example: use this criteria if you
need to know that your application is writing files
in a
specified directory. You can then check to see if
the oldest file is not older than 15 minutes (900
seconds). |
| Rule: Age oldest file (sec) - is greater
than - 900 |
| |
| Content |
| This criteria takes the entire content of a file
and lets you use the operator "contains" in both
case sensitive and case insensitive options to scan
through the contents of a file. |
| Usage example: use the rule Content - contains
(case-insensitive) - "error" to see get all locations
of the word "error". Use the alarm action keyword
"Matching text" to see all the complete lines where
the word "error" occured. |
| Rule: Content - contains
(case-insensitive) - error |
| |
| File access time |
| The time when the specified file (single file use
only) was last accessed (written/read). |
| Usage example: use this criteria to see
if an application is incorrectly reading or writing
a file when it
is not supposed to do so. If the time is greater
than the time when you manually access the file,
then the rule is broken and the application has accessed
the file. |
| Rule: File access time - is greater than
- 16:03:38 04/23/2002 |
| |
| File accessed |
| Returns a flag whether the specified file (single
file use only) has been accessed (Yes/No). |
| Usage example: use this criteria to see whether
a file has been accessed at all. If an application
is designed to write to an incremental log file every
15 minutes, you can use this criteria in a monitor
set for 30 minutes using this criteria which has
to be "Yes". |
| Rule: File accessed - equals - Yes |
| |
| File changed |
| Returns a flag whether the specified file (single
file use only) has been changed (Yes/No). |
| Usage example: use this criteria to see if a file
is changed and has grown since the last monitor update.
Combine this criteria with file size (bytes) to check
for file growth. |
| Rule: File changes - equals - Yes |
| |
| File count |
| The number of files when using a wildcard search
in a directory. This criteria does not count subdirectory
files. When a single file is specified, the file
count returns 0. |
| Usage example: use this criteria when you operate
two applications, one that writes files into a directory
and the other parses and deletes them. If the number
of files in the directory increases above 50, the
second application is probably having problems. |
| Rule: File count - is greater than - 50 |
| |
| File creation time |
| The time specifies when the file was created. If
the file path specification contains wildcards and
multiple files are monitored, the time shown is the
creation time of the oldest file. |
| Usage example: use this criteria to see if your
application has correctly started its log file recording
sequence at the correct date/time. |
| Rule: File creation time - is greater than - 16:03:38
04/23/2002 |
| |
| File name(s) |
| The name(s) of all monitored files according to
the file(s) path specification. When wildcards are
used, this value returns multiple comma seperated
names. |
| Usage example: mostly used in notifications, since
the files are already specified in the monitor. |
| |
| File size (bytes) |
| The total size of the file monitor file(s). If
the file path specification contains wildcards and
multiple files are monitored, the value is the sum
of all individual file sizes. |
| Usage example: use this criteria to check files
for size. If for instance a database file is bigger
than 2Gb, you may want to warn your network administrator. |
| Rule: File size (bytes) - is greater than - 2000000000 |
| |
| File path(s) |
| The path specification of the file(s) to monitor.
To specify multiple files, the path can contain wildcards. |
| Usage example: mostly used in notifications, since
the files are already specified in the monitor. |
| |
| Matching files(s) - only available in alarm actions |
| Returns the file containing the text searched for
in the content analysis. This keyword is only filled
when the rule is triggered on a content criteria.
When using a single file, this keyword will contain
the name of the specified file. |
| Usage example: alarm action (popup) - "Error value
occurred in file(s): <keyword>" |
| |
| Matching text - only available in alarm
actions |
| Returns the line or paragraph containing the string
specified in the content criteria of the rule. This
keyword is only filled when the rule is triggered
on a content criteria. |
| Usage example: alarm action (popup) - "Complete
line grep: <keyword>" |
File
analysis and characteristics