References > Component Monitor Types > File Monitors > File Change Monitor

File Change Monitor

This template tests if a file has been modified. The component monitor performs an MD5 checksum comparison on the file to verify it was not modified.

Prerequisites

None.

Statistic

The statistic is the number of hours since the file modification.

Credentials

Windows credential with read access to the network share and file.

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 filesystem 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 Linux system configurations for component monitors.

Monitored Components

For details on monitors, see SAM Component Monitor Types.

File Change Monitor

This component monitor tests if a file has been modified and then reports the time in hours since the file was modified as a statistic. The component monitor performs an MD5 checksum comparison on the file to verify it was not modified. If SolarWinds SAM detects the monitored file was modified, the component monitor will remain in a Down state until you recalculate the checksum. This component monitor uses TCP/445 and UDP/445 ports.