PRTG Manual: Exchange Database DAG (PowerShell) Sensor

Performance impact

This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.

Exchange user account permissions

This sensor requires 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:

• • Monitoring
  • View-Only Configuration
  • View-Only Recipients

Valid DAG

This sensor requires that the Exchange server is part of a valid DAG. For more information, see the Knowledge Base: Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell) sensor?

Remote PowerShell and Remote Exchange Management Shell

This sensor requires Remote PowerShell and Remote Exchange Management Shell on the target system and PowerShell on the probe system. 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.

For more information, see the Knowledge Base: How do I enable and use remote commands in Windows PowerShell? and How can I increase memory for Remote PowerShell?

.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node.

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

Parent device

This sensor requires that the parent device is the Exchange server (as of version 2016) that hosts the database that you want to monitor.

Credentials

This sensor requires credentials for Windows systems.

FQDN

This sensor requires the fully qualified domain name (FQDN) of the Exchange server in the settings of the parent device. In the device settings of the Exchange server, provide the FQDN instead of the IP address.

For more information, see the Knowledge Base: I have problems with the PowerShell Exchange sensors, what can I do?

IPv4

This sensor only supports IPv4.

Lookups

This sensor uses lookups to determine the status values of one or more channels.

Target device

Make sure that the Exchange database is mounted on the target device. Otherwise, you might not be able to properly add this sensor.

Knowledge Base

• Knowledge Base: Where can I find more information about PowerShell sensors?
• Knowledge Base: How can I monitor additional values of Exchange databases?

Hosted probe

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.

Database

The name of the database that this sensor monitors.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.
• Store result: Store the sensor result and the last response 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.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel 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 this sensor shows different channels:

• 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. PRTG stacks all channels with this unit 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.

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.