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, section Network Usage.

This sensor supports Unix line feeds.

To monitor files on a Linux system, the folder has to 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 by Paessler instance. If you want to use this sensor, add it to a remote probe device.

Requirement: LanmanServer ("Server") Windows Service

To monitor files on Windows shares, make sure that theLanmanServer ("Server") Windows 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.

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you do not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.

Sensor Settings

Click the Settings tab of a sensor to change its settings.

Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. See below for details on available settings.

Enter one or more tags, separated by spaces or commas. You can use tags to group sensors and use tag–filtered views later on. Tags are not case sensitive. We recommend that you use the default value.

There are default tags that are automatically predefined in a sensor's settings when you add a sensor. See section Default Tags below.

You can add additional tags to the sensor if you like. Other tags are automatically inherited from objects further up in the device tree. These are visible above as Parent Tags.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

Priority

Select a priority for the sensor. This setting determines where the sensor is placed in sensor lists. A sensor with a top priority is at the top of a list. Choose from one star (low priority) to five stars (top priority).

Default Tags

filesensor

Sensor Specific

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 looks for the target file only 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 server part (\\server\) is taken from the parent device settings of this sensor. Enter a valid path and file name.

To provide any Windows shares, the LanmanServer "Server" Windows service must run on the target computer.

To monitor any Linux files, the folder with these files has to be accessible via SMB.

Note that it might produce high 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 logfile for. You can enter a simple string in plain text or a regular expression.

The search string must be case sensitive.

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.The characters * and ? work as placeholders. * stands for no number or any number of characters and ? stands for exactly one character (as known from the Windows search). This behavior cannot be disabled, so the literal search for these characters is only possible using a regular expression.

Regular expression: Search using a regular expression (regex).

The pattern must be in one line and only the last matching line is returned.

Only transmit new lines at the end of the file (default): This option improves the performance of the sensor. It sends the whole file to PRTG only with the first scan. With the following sensor scans, the sensor only transmits lines that have been appended since the last scan. All other lines (that already existed in the previous scan) are not sent. The sensor assumes that they are unchanged and still counts them.This option is currently in beta status. Do not expect that it works as expected in every usage scenario.

Always transmit the entire file: The sensor sends the whole file to PRTG with every sensor scanning interval. If this results in too much traffic on the target system, we recommend that you choose the new lines option.

The sensor can only transmit newly added lines in the following cases:

Go into warning status when string is not found: The sensor shows a Warning status if there is no match. Otherwise it remains in an Up status.

Go into warning status when string is found: The sensor shows a Warning status if there is a match. Otherwise it remains in an Up status.

If Value Changes

Define what the sensor does when the sensor value changes:

Ignore changes (default): Take no action on change.

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.

The notification for this sensor is triggered when the value of the channel Last occurrence (line) changes. It is not triggered when the number of Matches changes.

Debug Options

Sensor Result

Define what PRTG does with the sensor results:

Discard sensor result: Do not store the sensor result.

Write sensor result to disk (file name: Result of Sensor [ID].txt): Store the last result received from the sensor to the \Logs\sensors subfolder of the PRTG data directory on the probe system (master node, if in a cluster). File names: Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This is for debugging purposes. PRTG overwrites these files with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG hosted by Paessler instance.

Sensor Display

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 the pin symbol of a channel on the sensor's Overview tab.

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.This option cannot be used in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This field 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.

Inherited Settings

By default, all of the following settings are inherited from objects that are higher in the hierarchy and should be changed there if necessary. Often, best practice is to change them centrally in the Root group's settings. For more information, see section Inheritance of Settings. To change a setting for this object only, disable inheritance by clicking the button next to inherit from under the corresponding setting name. You then see the options described below.

Select a scanning interval (seconds, minutes, or hours). The scanning interval determines the amount of time that the sensor waits between two scans. You can change the available intervals in the system administration on PRTG on premises installations.

If a Sensor Query Fails

Define the number of scanning intervals that the sensor has time to reach and check a device again in case a sensor query fails. Depending on the option that you select, the sensor can try to reach and check a device again several times before the sensor shows a Downstatus. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows a Warning status. Choose from:

Set sensor to down immediately: Set the sensor to a Down status immediately after the first failed request.

Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to a Warning status after the first failed request. If the following request also fails, the sensor shows an error.

Set sensor to warning for 2 intervals, then set to down: Set the sensor to a Down status only after three consecutively failed requests.

Set sensor to warning for 3 intervals, then set to down: Set the sensor to a Down status only after four consecutively failed requests.

Set sensor to warning for 4 intervals, then set to down: Set the sensor to a Down status only after five consecutively failed requests.

Set sensor to warning for 5 intervals, then set to down: Set the sensor to a Down status only after six consecutively failed requests.

Sensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show a Down status. It is not possible to immediately set a WMI sensor to a Down status, so the first option does not apply to these sensors. All other options can apply.

If you define error limits for a sensor's channels, the sensor immediately shows a Down status. No "wait" option applies.

If a channel uses lookup values, the sensor immediately shows a Down status. No "wait" options apply.

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 settings here. They are active at the same time as the parent objects' settings.

Schedule

Select a schedule from the list. Schedules can be used to monitor for a certain time span (days or hours) every week.

You can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Account Settings—Schedules.

Schedules are generally inherited. New schedules are added to existing schedules, so all schedules are active at the same time.

Maintenance Window

Specify if you want to set up a one-time maintenance window. During a maintenance window, the current object and all child objects are not monitored. They are in a Pausedstatus instead. Choose between:

Not set (monitor continuously): No maintenance window is set and monitoring is always active.

Set up a one-time maintenance window: Pause monitoring within a maintenance window. You can define a time span for a monitoring pause below and change it even for a currently running maintenance window.

To terminate a current maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

This field is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the maintenance window.

Maintenance Ends

This field is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the maintenance window.

Dependency Type

Define a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:

Use parent: Use the dependency type of the parent object.

Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if a specific sensor is in a Down status or in a Paused status caused by another dependency.

Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in a Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.

To test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.

Dependency

This field is only visible if you enable Select a sensor above. Click the Search button and use the object selector to select a sensor on which the current object will depend.

Dependency Delay (Sec.)

This field is only visible if you enable Select a sensor above. Define a time span in seconds for dependency delay.

After the master sensor for this dependency comes back to an Up status, monitoring of the dependent objects is additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Enter an integer value.

This setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.

Define the user groups that have access to the selected object. A table with user groups and types of access rights is shown. It contains all user groups from your setup. For each user group, you can choose from the following access rights:

Inherited: Use the access rights settings of the parent object.

None: Users in this group cannot see or edit the object. The object neither shows up in lists nor in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree but it cannot be accessed.

Read: Users in this group can see the object and review its monitoring results.

Write: Users in this group can see the object, review its monitoring results, and edit its settings. They cannot edit access rights settings.

Full: Users in this group can see the object, review its monitoring results, edit its settings, and edit access rights settings.

You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option.

To change display settings, spike filtering, and limits, switch to the sensor's Overview tab and click the gear icon of a specific channel. For detailed information, see section Sensor Channel Settings.