Documentation forHybrid Cloud Observability Essentialsand Server & Application Monitor

File Existence Monitor

The File Existence Monitor is a SAM component monitor included in several SAM application monitor template that you can assign to a target servers to test if a file exists at a specific location on that server.

By default, it uses the following ports:

  • TCP port 445
  • UDP port 445

Prerequisites

None.

Credentials

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 dumpfile.

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.

Troubleshooting tips

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.