File Age Monitor
The File Age Monitor is a SAM component monitor included in several SAM application monitor templates that you can assign to a node to determine when a specific file was last modified. Using ports 445 (TCP) and 445 (UDP), it tracks the number of elapsed hours since the file modification date.
To learn how to use wildcards to check the age of a specific file type and define how many minutes old a file can be, see File Age Monitor (Wildcard) in THWACK.
The statistic is the number of elapsed hours since the file modification date.
Agent-less or Orion Platform agent for Windows requirements
Windows credentials with read access to the network share and file.
WMI or Windows file share access to the target machine.
Orion Platform agent for Linux requirements
Python implementation leverages native file system access directly from the Python script that runs locally on the target agent machine.
To leverage this monitor against a Linux system, the Orion Platform Agent for Linux is required. This means that the Linux machine you plan to monitor must have the Linux agent installed, and that the node is managed using the agent within the Orion Platform.
A default description of the monitor. To override the default description, add to or replace existing text. Changes are automatically saved. The variable to access this field is
Customize descriptions to specify what will be monitored so related alerts and notifications are more meaningful later.
Determines if the component is enabled. Disabling the component leaves it in a deactivated state that does not influence its application availability or status, as displayed in the Orion Web Console.
Credential for Monitoring
Select a credential with read access to the file or use the <Inherit credential from node> option. If the credential you need is not in the credentials list, add it in the Credentials Library. See Understand the Credentials Library for details.
The full path where the file is stored on the target system.
Select this option to mathematically convert returned values through the use of data transformations. See Convert values in data transformations for SAM component monitors.
Specify a threshold that indicates a warning level was breached. Logical operators are in the drop-down list, followed by a blank field where you can enter the value of this threshold. For example:
Less than 15 for warning,
Less than 5. for critical. See Application Monitor Thresholds.
Add notes for easy reference. You can access this field by using the variable,