<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Local Folder Sensor

i_betaThis sensor is in beta status. The operating methods and the available settings can change at any time. Do not expect that all functions work properly, or that this sensor works as expected at all. Be aware that this sensor can be removed from PRTG at any time.

i_round_blueTo use this sensor, enable the Beta Sensors experimental feature of PRTG. For more information, see the Knowledge Base: What are beta sensors and how can I use them?

The Local Folder sensor monitors a local folder on a probe system.

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Local Folder Sensor

Local Folder Sensor

Sensor in Other Languages

  • Dutch: Local Folder
  • French: Local Folder
  • German: Local Folder
  • Japanese: Local Folder
  • Portuguese: Local Folder
  • Russian: Local Folder
  • Simplified Chinese: Local Folder
  • Spanish: Local Folder

Remarks

  • You can only create this sensor on a probe device, either a local probe device or a remote probe device.

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

Add Sensor

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. Therefore, you do not see all settings. You can change nearly all settings on the sensor's Settings tab after creation.

Basic Sensor Settings

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

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

Sensor Name

Enter a meaningful name to identify the sensor.

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

i_round_blueThis setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, the Enter key, or a comma. You can use tags to group objects and use tag-filtered views. Tags are not case sensitive. Tags are automatically inherited.

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

i_round_blueFor performance reasons, it can take some minutes until you can filter for new tags.

The sensor has the following default tags:

  • filesystem
  • folder

Priority

Select a priority for the sensor. The priority determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority (i_priority_1) to the highest priority (i_priority_5).

Local Folder Specific

Local Folder Specific

Local Folder Specific

Setting

Setting

Path

Enter the path of the folder that you want to monitor. For example, enter C:\Windows. The folder must exist on the probe system.

i_round_blueThe sensor only supports local paths.

Timeout (Sec.)

Enter a timeout in seconds. If the scan of the folder takes longer, the sensor cancels the request and shows an error message. If two consecutive scans fail, the sensor shows the Down status. The default value is 300 seconds (5 minutes).

Recurse Subfolders

Specify if the sensor includes subfolders in the folder monitoring. Choose between:

  • Do not recurse subfolders: Only monitor the folder. Do not monitor its subfolders.
  • Monitor the folder and its subfolders (recursive): Monitor the folder and all of its subfolders.
    i_round_redIf you recurse subfolders in large directories that have a high number of branches, this may cause timeout errors or performance issues.

Filter by File Name

Select if you want to filter by file name. Choose between:

  • Disable (default): Do not filter by file name.
  • Include filter: The sensor counts files that match the File Filter.
  • Exclude filter: The sensor counts files that do not match the File Filter.

File Filter

This field is only visible if you select Include filter or Exclude filter above. Enter a comma-separated list of file names, file formats, or patterns you want to filter for. For example, '*.pdf,*.docx' includes or excludes files with the file formats .pdf or .docx.

i_round_blueThe file filter is not case sensitive and supports wildcards (*).

File Age Filter

Select if you want to filter by file age. Choose between:

  • Disable (default): Do not filter by file age.
  • Enable: Filter by file age.

Newer Than

This field is only visible if you select Enable above. Enter a file age. The sensor only counts files that are younger than this age.

i_round_blueLeave this field empty if you only want to filter for files with the Older Than setting.

Older Than

This field is only visible if you select Enable above Enter a file age. The sensor only counts files that are older than this age.

i_round_blueLeave this field empty if you only want to filter for files with the Newer Than setting.

File Age Filter Unit

This field is only visible if you select Enable above. Select the time unit that you want to use for the File Age Filter. Choose between:

  • Days (default)
  • Hours
  • Minutes

Sensor Display

Sensor Display

Sensor Display

Setting

Setting

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how to display channel graphs:

  • 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.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling in the channel settings.

Stack Unit

This setting is only visible if you select Stack channels on top of each other as Graph Type. Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use this unit. However, there is an advanced procedure to do so.

Debug Options

Debug Options

Debug Options

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 name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Inherited Settings

By default, all of the following 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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Click b_inherited_enabled to disable the inheritance.

Scanning Interval

Scanning Interval

Setting

Setting

Scanning Interval

Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:

  • 60 seconds
  • 5 minutes
  • 10 minutes
  • 15 minutes
  • 30 minutes
  • 1 hour
  • 4 hours
  • 6 hours
  • 12 hours
  • 24 hours

i_round_blueYou can change the available intervals in the system administration of PRTG Network Monitor.

i_round_blueThe minimum scanning interval is 1 minute.

i_round_blueThe recommended scanning interval is 5 minutes.

If a Sensor Query Fails

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

  • Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
  • Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
  • Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
  • Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
  • Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
  • Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.

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

i_round_blueIf you define error limits for channels, the sensor immediately shows the Down status. None of the interval options apply.

i_round_blueIf a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.

Schedules, Dependencies, and Maintenance Windows

i_round_blueYou cannot disable 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.

Schedules, Dependencies, and Maintenance Windows

Schedules, Dependencies, and Maintenance Windows

Setting

Description

Schedule

Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:

  • None
  • Saturdays
  • Sundays
  • Weekdays
  • Weekdays Eight-To-Eight (08:00 - 20:00)
  • Weekdays Nights (17:00 - 09:00)
  • Weekdays Nights (20:00 - 08:00)
  • Weekdays Nine-To-Five (09:00 - 17:00)
  • Weekends

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

Maintenance Window

Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the object and all child objects. They show the Paused status instead. Choose between:

  • Do not set up a one-time maintenance window: Do not set up a one-time maintenance window. Monitoring is always active.
  • Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for the maintenance window below.

i_round_blueTo terminate an active maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

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

Maintenance Ends

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

Dependency Type

Select 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 the Down status or in the Paused status because of 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 the 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.

i_round_blueTo 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 setting is only visible if you enable Select a sensor above. Click b_search_light and use the object selector to select a sensor on which the current object will depend.

Dependency Delay (Sec.)

This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay.

After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.

i_round_redThis setting is not visible if you select Use parent or Master sensor for parent. In this case, define delays in the parent device settings or parent group settings.

Access Rights

Click b_inherited_enabled to disable the inheritance.

Access Rights

Access Rights

Setting

Description

User Group Access

Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:

  • Inherited: Inherit the access rights settings of the parent object.
  • No access: Users in this user group cannot see or edit the sensor. The sensor neither shows up in lists nor in the device tree.
  • Read access: Users in this user group can see the sensor and view its monitoring results. They cannot edit any settings.
  • Write access: Users in this user group can see the sensor, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
  • Full access: Users in this user group can see the sensor, view its monitoring results, edit its settings, and edit its access rights settings.

i_square_cyanFor more details on access rights, see section Access Rights Management.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the monitored 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 in percent.

File Count

The number of files in the folder

i_round_redThe sensor counts all files in a folder, including hidden files.

i_round_blueThis channel is the primary channel by default.

Folder Count

The number of folders

Folder Size

The folder size in bytes

Newest File

The time since the newest modification of a file in the folder (newest file)

i_round_blueThe sensor shows a negative value if the date of a modified file is in the future.

Oldest File

The time since the oldest modification of a file in the folder (oldest file)

More

i_square_blueKnowledge Base

What are beta sensors and how can I use them?

What do I need to know about beta sensors?

What security features does PRTG include?

Sensor Settings Overview

For more information about sensor settings, see the following sections: