PRTG Manual: Exchange Database (PowerShell) Sensor
The Exchange Database (PowerShell) sensor monitors database information of an Exchange server using Remote PowerShell.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Exchange Database (PowerShell)
- French: Base de données Exchange (PowerShell)
- German: Exchange-Datenbank (PowerShell)
- Japanese: Exchange データベース(PowerShell)
- Portuguese: Banco de dados do Exchange (PowerShell)
- Russian: База данных Exchange (PowerShell)
- Simplified Chinese: Exchange 数据库 (PowerShell)
- Spanish: Base de datos de Exchange (PowerShell)
- 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.
- The parent device for this sensor must be the Exchange server (version 2010 or higher) that hosts the database that you want to monitor.
- This sensor requires Remote PowerShell and Remote Exchange Management Shell on the target servers and PowerShell 2.0 on the probe system.
- This sensor requires the fully qualified domain name (FQDN) of the Exchange server in the settings of the parent device.
- This sensor requires .NET 4.7.2 or later on the probe system.
- This sensor requires credentials for Windows systems in the settings of the parent device.
- See the Knowledge Base: Where can I find more information about PowerShell sensors?
- See the Knowledge Base: How can I monitor additional values of Exchange databases?
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 |
---|---|
Remote PowerShell and Remote Exchange Management Shell |
This sensor uses PowerShell commands. To monitor Exchange servers with this sensor, you have to enable Remote PowerShell and Remote Exchange Management Shell on the target servers that you want to monitor. Also ensure you have installed PowerShell 2.0 or later on the probe system.
|
FQDN |
To connect to Exchange servers, this sensor needs the FQDN. In the device settings of the Exchange server, provide the FQDN instead of the IP address.
|
.NET Framework |
This sensor requires the Microsoft .NET Framework. .NET 4.7.2 or later must be installed on the probe system (on every cluster node, if on a cluster probe). If the framework is missing, you cannot create this 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.
Select the databases that you want to monitor. PRTG creates one sensor for each database that you select in the Add Sensor dialog. The settings you select are valid for all sensors that you create when you finish this dialog.
The following settings in the Add Sensor dialog differ in comparison to the sensor's Settings tab.
Sensor Settings
Setting |
Description |
---|---|
Databases |
Select the databases that you want to add a sensor for. You see a list with the names of all items that you can monitor. Add check marks in front of the respective lines to select the desired items. You can also use the check box in the table header to select all items or cancel the selection.
|
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.
Setting |
Description |
---|---|
Sensor Name |
Enter a meaningful 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. 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.
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 ( |
Setting |
Description |
---|---|
Database |
Shows the name of the monitored database. Once you have created the sensor, you cannot change this value. It is shown for reference purposes only. If you need to change this value, add the sensor anew. |
AutoRemount Database |
Define if you want the sensor to try to automatically remount the database if it is unmounted:
|
Result Handling |
Define what PRTG does with the sensor result:
|
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:
|
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 the following settings are inherited from objects that are higher in the hierarchy. You should 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. You then see the options described below.
For more information, see section Inheritance of Settings.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
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:
|
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:
|
Schedules, Dependencies, and Maintenance Windows
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.
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:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting 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 one-time maintenance window. |
Maintenance Ends |
This setting 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 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:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you enable 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.
|
Click to interrupt the inheritance.
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:
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available):
|
Which channels the sensor actually shows might depend on the monitored device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Database Size |
The size of the database in bytes
|
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. |
Is Valid |
If the database is recognized as valid
|
Mounted |
If the database is mounted
|
KNOWLEDGE BASE
Where can I find more information about PowerShell sensors?
How can I monitor additional values of Exchange databases?
How do I enable and use remote commands in Windows PowerShell?
How can I increase memory for Remote PowerShell?
I have problems with the PowerShell Exchange sensors, what can I do?
Which .NET version does PRTG require?
What security features does PRTG include?
My PowerShell sensor returns an error message. What can I do?
I get the error "WinRM cannot process the request" when I try to use a PowerShell sensor
For more information about sensor settings, see the following sections: