Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Exchange 2016 Hub Transport Role Counters (Advanced)

This SAM application monitor template contains advanced performance and statistics counters for monitoring Exchange 2016 Hub Transport Role. Some counters (indicated by (database) in their name) may require manual configuration, such as setting up installation-specific instances, correcting thresholds for the client’s environment, and so forth. To assist with the creation of these, Use the Component Monitor Wizard in SAM.

You can also use this template in addition to the Exchange 2016 Hub Transport Role Services and Counters (Basic) template.

Components that are specific to a database are disabled by default. If you want to monitor database specific metrics, please re-enable these components, and provide the instance specific information, or utilize the Use the Component Monitor Wizard in SAM to add the database specific counters you desire to the existing template/application.

Prerequisites

PowerShell 5.1 is installed on target servers.

RPC and WMI access to the Exchange server.

Credentials

Windows Administrator on target server.

Component monitors

Dumpster Size

Shows the total size (in bytes) of mail items currently in the transport dumpster on this server.

Dumpster Inserts/sec

Shows the rate at which items are inserted into the transport dumpster on this server. Determines the current rate of transport dumpster inserts.

Dumpster Item Count

Shows the total number of mail items currently in the transport dumpster on this server. Shows the current number of items being held in the transport dumpster.

Dumpster Deletes/sec

Shows the rate at which items are deleted from the transport dumpster on this server. Determines the current rate of transport dumpster deletions.

I/O Log Writes/sec (database)

Shows the rate of log file write operations completed. Determines the current load. Compare values to historical baselines.

I/O Log Reads/sec (database)

Shows the rate of log file read operations completed. Determines the current load. Compare values to historical baselines.

Log Generation Checkpoint Depth (database)

Represents the amount of work (in count of log files) that needs to be redone or undone to the database files if the process fails.

Should be less than 1,000 at all times.

I/O Database Reads/sec (database)

Shows the rate of database read operations completed. Determines the current load. Compare values to historical baselines.

I/O Database Writes/sec

Shows the rate of database write operations completed. Determines the current load. Compare values to historical baselines.

Messages Submitted Per Second

Shows the number of messages queued in the Submission queue per second. Determines current load. Compare values to historical baselines.

Messages Received/sec

Shows the number of messages received by the SMTP server each second. Determines current load. Compare values to historical baselines.

Messages Sent/sec

Shows the number of messages sent by the SMTP send connector each second. Determines current load. Compare values to historical baselines.

Messages Queued for Delivery Per Second

Shows the number of messages queued for delivery per second. Determines current load. Compare values to historical baselines.

Messages Completed Delivery Per Second

Shows the number of messages delivered per second. Determines current load. Compare values to historical baselines.

Avg. Disk sec/Read (Physical Disk)

Shows the average time, in seconds, of a read of data from the disk.

Should be less than 20 milliseconds (ms) on average. Spikes (maximum values) should not be higher than 50 ms.

When looking at hard disks using perfmon.exe, an understanding of the underlying hard disk subsystem is required to determine which counters (physical disk or logical disk) to look at.

Avg. Disk sec/Write (Physical Disk)

Shows the average time, in seconds, of a write of data to the disk.

Should be less than 20 milliseconds (ms) on average. Spikes (maximum values) should not be higher than 50 ms.

When looking at hard disks using perfmon.exe, an understanding of the underlying hard disk subsystem is required to determine which counters (physical disk or logical disk) to look at.

Avg. Disk sec/Read (Logical Disk)

Shows the average time, in seconds, of a read of data from the disk.

Should be less than 20 milliseconds (ms) on average. Spikes (maximum values) should not be higher than 50 ms.

When looking at hard disks using perfmon.exe, an understanding of the underlying hard disk subsystem is required to determine which counters (physical disk or logical disk) to look at.

Avg. Disk sec/Write (Logical Disk)

Shows the average time, in seconds, of a write of data to the disk.

Should be less than 20 milliseconds (ms) on average. Spikes (maximum values) shouldn't be higher than 50 ms.

When looking at hard disks using perfmon.exe, an understanding of the underlying hard disk subsystem is required to determine which counters (physical disk or logical disk) to look at.

Retry Non-Smtp Delivery Queue Length

Shows the number of messages in a retry state in the non-SMTP gateway delivery queues.

Should not exceed 100.

Largest Delivery Queue Length

Shows the number of messages in the largest delivery queues.

Should be less than 200 for the Edge Transport and Hub Transport server roles.

Version buckets allocated (database)

Total number of version buckets allocated. Shows the default backpressure values as listed in the edgetransport.exe.config file.

Should be less than 200 at all times.

Log Record Stalls/sec (database)

Shows the number of log records that cannot be added to the log buffers per second because they are full. If this counter is nonzero most of the time, the log buffer size may be a bottleneck.

Should be less than 10 per second on average. Spikes (maximum values) should not be greater than 100 per second.

Log Threads Waiting (database)

Shows the number of threads waiting for their data to be written to the log to complete an update of the database. If this number is too high, the log may be a bottleneck.

Should be less than 10 threads waiting on average.