PRTG Manual: Exchange Database DAG (PowerShell) Sensor
<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> 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.
Exchange Database DAG (PowerShell) Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
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)
Remarks
This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
This sensor requires Exchange user account permissions.
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.
Detailed Requirements
Requirement
Description
Exchange user account permissions
This sensor requires a user account that must be either in the Exchange management role groupView-Only Organization Managementor be in a group with the following assigned management roles:
Monitoring
View-Only Configuration
View-Only Recipients
Remote PowerShell and Remote Exchange Management Shell
This sensor uses PowerShell commands. This sensor requires that Remote PowerShell and Remote Exchange Management Shell are enabled on the target systems that you want to monitor. Also make sure you have at least PowerShell 2.0 installed on the probe system.
In larger environments, the default memory limit for the remote shell might be insufficient. This might result in the error message The WSMan provider host process did not return a proper response. In this case, increase the memory limit for Remote PowerShell.
To connect to Exchange servers, this sensor requires the FQDN. In the device settings of the Exchange server, provide the FQDN instead of the IP address.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
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.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
exchange
powershell
database
dag
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 () to the highest priority ().
Sensor Settings
Sensor Settings
Setting
Description
Database
The name of the database that this sensor monitors.
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, Result of Sensor [ID].Data.txt, and Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
Sensor Display
Sensor Display
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.
You can set a different primary channel later by clicking below a channel gauge 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. You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
Stack Unit
This setting is only visible if you select Stack channels on top of each other above.
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 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 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.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel List
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
Up status: No
Warning status: Yes
Active Copy
The copy status
Up status: Active, Not Active
Warning status: Active But Not On The Preferred Server, Could Not Read Activation Preference, Not Active But This Is The Preferred Server
Content Index State
The content index status
Up status: Healthy, Not Supported In 2019
Warning status: Crawling
Down status: Error
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
Log Copy Queue Increasing
If the log copy queue is increasing
Up status: No
Warning status: Yes
Log Replay Queue Increasing
If the log replay queue is increasing
Up status: No
Warning status: Yes
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
Up status: Healthy, Mounted
Warning status: Disconnected and Healthy, Disconnected and Resynchronizing, Dismounting, Initializing, Mounting, Resynchronizing, Seeding, SeedingSource, SinglePageRestore, Suspended
Down status: Dismounted, Failed, Failed and Suspended, Service Down
This channel is the primary channel by default.
More
KNOWLEDGE BASE
Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell) sensor?