PRTG Manual: Exchange Database DAG (PowerShell) Sensor
The Exchange Database DAG (PowerShell) sensor monitors the Database Availability Group (DAG) status of a database on an Exchange server via Remote PowerShell.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Exchange Database DAG (PowerShell)
- French: Exchange base de données DAG (PowerShell)
- German: Exchange-Datenbank DAG (PowerShell)
- Japanese: Exchange データベース DAG(PowerShell)
- Portuguese: Banco de dados DAG Exchange (PowerShell)
- Russian: DAG базы данных Exchange (PowerShell)
- Simplified Chinese: Exchange 数据库 DAG (PowerShell)
- Spanish: Base de datos DAG 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.
- The Exchange server must be part of a valid DAG. See also the Knowledge Base: Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell) sensor?
- This sensor requires Remote PowerShell and Remote Exchange Management Shell on the target servers and PowerShell on the probe system.
- This sensor requires credentials for Windows systems in the settings of the parent device.
- This sensor requires Exchange user account permissions.
- This sensor requires the fully qualified domain name (FQDN) of the Exchange server in the settings of the parent device.
- This sensor requires Microsoft .NET 4.7.2 or later on the probe system.
- Make sure that the Exchange database is mounted on the target device. Otherwise, you might not be able to properly add the sensor.
- This sensor only supports the IPv4 protocol.
- This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
- 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 must 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.
|
Exchange user account permissions |
This sensor requires a user account that must be either in the Exchange management role group View-Only Organization Management or be in a group with the following assigned management roles:
|
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 4.7.2 or later |
This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).
|
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.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
Sensor Settings
Setting |
Description |
---|---|
Databases |
Select the databases that you want to monitor. PRTG creates one sensor for each database that you select.
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. |
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:
|
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 ( |
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
Setting |
Description |
---|---|
Database |
Shows the name of the database that this sensor monitors.
|
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 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 |
---|---|
Activation Suspended |
If the activation is suspended
|
Active Copy |
The copy status
|
Content Index State |
The content index state
|
Copy Queue Length |
The number of items in the copy queue |
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. |
Log Copy Queue Increasing |
If the log copy queue is increasing
|
Log Replay Queue Increasing |
If the log replay queue is increasing
|
Replay Queue Length |
The number of items in the replay queue |
Single Page Restore |
The number of single page restores |
Status |
The overall DAG status
|
Knowledge Base
Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell) sensor?
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