PRTG Manual: File Content Sensor
The File Content sensor checks a text file (for example, a log file) for certain strings.
Additionally, the 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. Use it with care. We recommend that you use no more than 200 sensors of this sensor type on each probe.
▪This sensor requires that the LanmanServer service runs on the target computer.
▪This sensor does not support UTF-16 encoded files. In this case, try to use a custom sensor like the EXE/Script sensor or the EXE/Script Advanced sensor.
▪This sensor does not officially support binary files. If you would still like to monitor binary files contrary to our recommendation, choose the option Always transmit the entire file in the sensor settings, option File Transmission Handling.
▪This sensor supports Unix line feeds.
▪This sensor supports the IPv6 protocol.
▪To monitor files on a Linux system, the folder must be accessible via Server Message Block (SMB).
▪Try using the fully qualified domain name (FQDN) of the target device 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 |
---|---|
LanmanServer service |
To monitor shares on Windows machines, make sure that the LanmanServer service runs on the target computer.
To enable the service, log in to the respective computer and open the services manager (for example, via services.msc). In the list, find the respective service and set its Start Type to Automatic. |
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
Click the Settings tab of a sensor to change its settings.
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.
|
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe.
|
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor: ▪filesensor |
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 ( |
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\johnqpublic\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.
|
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).
|
Search Method |
Define the method with which you want to provide the search string: ▪Simple string search: Search for a simple string in plain text.
▪Regular expression: Search with a regex.
|
File Transmission Handling |
Define in which way the sensor transmits the target file to PRTG: ▪Only transmit new lines at the end of the file (default): Send the entire file to PRTG only with the first scanning interval. With the following scanning intervals, the sensor only transmits new lines at the end of the file. It does not send old lines but it still counts them. This option improves the performance of the sensor. ▪Always transmit the entire file: Send the entire file to PRTG with every sensor scanning interval. If this results in too much traffic on the target system, we recommend that you choose Only transmit new lines at the end of the file (default) instead. The sensor can only transmit new lines in the following cases: ▪the file is bigger than in the previous scanning interval, and ▪the last line in the file is still in the same place in the file.
|
File Encoding |
Specify the encoding of the file that this sensor monitors: ▪Windows-1252 (default) ▪UTF-8 ▪UTF-16 |
Sensor Behavior |
Define the condition for which the sensor shows the Warning status: ▪Show warning status when the string is not found: Show the Warning status if there is no match. Otherwise it remains in the Up status. ▪Show warning status when the string is found: Show the Warning status if there is a match. Otherwise it remains in the Up status. |
If Value Changes |
Define what the sensor does if the value of the Last Occurrence (Line) channel changes ▪Ignore changes (default): Do nothing. ▪Trigger 'change' notification: Send an internal message indicating that the sensor value has changed. In combination with a change trigger, you can use this mechanism to trigger a notification whenever the sensor value changes.
|
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result: ▪Discard result: Do not store the sensor result. ▪Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.
|
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.
|
Graph Type |
Define how different channels are shown for this sensor: ▪Show channels independently (default): Show a graph for each channel. ▪Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic. |
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. 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.
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
|
Matches |
The number of matches |
KNOWLEDGE BASE
What security features does PRTG include?