PRTG Manual: File Content Sensor
The File Content sensor checks a text file (for example, a log file) for certain strings.
Additionally, this sensor quotes matching lines in the sensor message.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Bestands inhoud
- French: Contenu du fichier
- German: Datei-Inhalt
- Japanese: ファイルの内容
- Portuguese: Conteúdo de arquivo
- Russian: Содержимое файла
- Simplified Chinese: 文件内容
- Spanish: Contenido de archivo
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires that the LanmanServer service runs on the target system.
- This sensor does not support UTF-16 encoded files. Try a custom sensor like the EXE/Script sensor or the EXE/Script Advanced sensor.
- This sensor does not officially support binary files. If you want to monitor them anyway, select Always transmit the entire file in the sensor settings.
- This sensor supports Unix line feeds.
- This sensor supports IPv6.
- To monitor files on a Linux system, the folder must be accessible via Server Message Block (SMB).
- Try the fully qualified domain name (FQDN) of the target system if the sensor does not get a connection with the IP address.
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
Requirement |
Description |
---|---|
To monitor shares on Windows machines, this sensor requires that the LanmanServer service runs on the target system. The display name of the service is Server. To enable the service, log in to the respective system and open the services manager (for example, via services.msc). In the list, find the respective service and set its Start Type to Automatic. |
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets. If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include? |
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is for your information only. You cannot change it. |
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited. It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>). For performance reasons, it can take some minutes until you can filter for new tags that you added. The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority (). |
Setting |
Description |
---|---|
File Name |
Enter the full path to the file that this sensor monitors. For example, enter C:\Windows\file.txt. to monitor a file on the probe system. If you use a local path, the sensor only looks for the target file on the probe system, not on the parent device. To monitor a file on the parent device, use the dollar sign ($) like C$\User\username\file.txt. If the file is located on a network device, use the Universal Naming Convention (UNC) path without the server part (only enter share\folder\file.txt). The sensor inherits the server part (\\server\) from the parent device settings. Enter a valid path and file name. To monitor Windows shares, the LanmanServer service must run on the target computer. To monitor Linux files, the folder with these files must be accessible via SMB. Note that it might produce a high amount of network traffic if you define that PRTG queries an entire file on your network with every scanning interval. |
Search String |
Define the string that you want to search the file for. You can enter a simple string in plain text or a regular expression (regex). The search string must be case-sensitive. |
Search Method |
Define the method with which you want to provide the search string:
The characters * and ? work as placeholders. * stands for no number or any number of characters and ? stands for exactly one character. You cannot change this behavior. The literal search for these characters is only possible with a regex.
The pattern must be in one line and only the last matching line is returned. PRTG supports Perl Compatible Regular Expression (PCRE) regex. For more information, see section Regular Expressions. |
Define in which way the sensor transmits the target file to PRTG:
This sensor can only transmit new lines in the following cases:
This sensor supports Windows and Linux line endings (CRLF or. LF). |
|
File Encoding |
Specify the encoding of the file that this sensor monitors:
|
Sensor Behavior |
Define the condition for which the sensor shows the Warning status:
|
If Value Changes |
Define what the sensor does if the value of the Last Occurrence (Line) channel changes:
This sensor does not trigger the notification when the number of Matches changes. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
In a cluster, PRTG stores the result in the PRTG data directory of the master node. |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor. You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab. |
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window (default).
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Last Occurrence (Line) |
The line number of the last match This channel is the primary channel by default. |
Matches |
The number of matches |
KNOWLEDGE BASE
What security features does PRTG include?