File Existence Monitor
The File Existence Monitor is a SAM component monitor that is also available as a SAM template that can test if a file exists at a specific location on a target server. It uses ports TCP/445 and UDP/445.
You can use this template in conjunction with other File templates. For example, use it with the File Count template to count how many files in a directory have a specific extension, and then set up thresholds and alerts based on the value.
Windows credentials with read access to the network share.
Agent-less or Orion agent for Windows requirements
Implementation of these components relies either on WMI or Windows File Share access to the target machine.
Orion agent for Linux requirements
Python implementation leverages native file system access directly from the python script running locally on the target agent machine. Due to the configuration settings, switching between agent-less and Orion agent for Linux will not establish a correct connection as the file path in UNC format will not work on a Linux-based computer. For details, see Configure Linux/Unix systems for monitoring by the Orion agent in SAM.
File Existence Monitor details
- You can use wildcards in path statements. For example, specify
\\dumpserver\c$\dump\dumpfile*.*to check for all files that start with
- The Component Type value for this component monitor, for use in alert variables, is 28. To learn more, see Use alerts to monitor your environment or watch a SolarWinds Lab Bits video, Automating Alert Trigger Actions.
If you receive a
There are currently no logon servers available to service the logon request message, try these workarounds:
- Add the IP address of the target node to the host file of your Main Polling Engine (usually the Orion server), or an Additional Polling Engine (APE), depending on where the node is assigned.
- Add the IP address of the assigned polling engine to the host file on the target machine, which can help bypass DNS issues.