File Monitor is a fundamental IPNetwork’s Monitor enabling local or remote file size queries and alerts based on the returned value (scaled, if necessary). Various issues can be identified by monitoring a known file size. Manually checking file size is possible with built-in file system commands. However, querying remote file sizes can be cumbersome; automating this requires parsing output to get the needed value. IPNetwork Monitor offers a straightforward yet powerful interface for querying file sizes. Creating a File Monitor is simple: enter the UNC (Uniform Naming Convention, e.g., \\host\share\resource) file name and access credentials (domain, username, and password). You can also specify a divisor to scale the returned value appropriately. Configure availability and performance parameters on the State conditions tab to perform the actual verification. Use Cases
  • Mailbox Size Monitoring. A common use for the file size monitor is ensuring inboxes stay within a reasonable size limit. Overly large inboxes increase server load as the mail service manages them. Automated mailbox processing issues can also be indicated by excessive size.
  • Log File Size Management. Network and other services frequently generate log files, often rotated daily for backup and activity tracking. Excessive log file growth can signify abnormal behavior or high service load, requiring administrator attention.
  • Backup Verification. Regular data backups are crucial. This monitor can observe backup media, ensuring data file sizes are within expected ranges. A failed condition could indicate a backup failure, demanding immediate action.
  • Critical File Monitoring. Some files, such as configuration files, encrypted storage, or password files, must remain unaltered. Changes in size or timestamp could indicate tampering, a serious security concern.
  • General Quota Management. In scenarios like database engines, maintaining file size within limits is important. Exceeding these limits might suggest an anomaly, such as a database requiring optimization.
A file size monitor can trigger more resource-intensive monitors. For instance, if a mailbox exceeds a size threshold, a custom script monitor can execute to perform further checks. Running such scripts regularly might be excessive, but triggering them based on file size is efficient. File size checks are significantly faster than SNMP or WMI queries designed for the same purpose. Prioritize efficient, less resource-intensive monitor types whenever feasible. This holds true for file size monitors: use simpler methods if possible to avoid querying remote file systems. Appropriate scaling is also usually necessary for clear monitor interpretation.   [interfaces_screenshot]