exchange_monitor submission queue and unreachable queue length not available on Edge Servers
search cancel

exchange_monitor submission queue and unreachable queue length not available on Edge Servers


Article ID: 263909


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


We deployed 16 Exchange_monitor probes on local Servers windows 2022 all running Exchange Server 2019. 

8 Are Mailboxes Servers and the Servers

Other 8 are Edge Transport Servers only, without a mailbox.
On the 8 Mailboxes servers there is no issue. 
On the 8 Edge Servers the "submission queue length " and the "unreachable queue length" do NOT show in the STATUS tab so they are not monitored. 
On this server, the queue is returned by the > Get-QUEUE command: 
We have already ruled out the known issue documented in the below KB:
What are we missing? 
How can we enable "submission queue length " and the "unreachable queue length" monitoring on the Edge Servers similarly to what we already do with the Mailboxes servers?


UIM 20.4
Windows 2022 OS 
Exchange servers 2019


Missing hub transport role


The probe uses the below registry path to fetch the affected counters.

RegOpenKeyEx HKLM\Software\Microsoft\ExchangeServer\v15\MailboxRole failed (The system cannot find the file specified.
RegOpenKeyEx HKLM\Software\Microsoft\ExchangeServer\v15\HubTransportRole failed (The system cannot find the file specified.
RegOpenKeyEx HKLM\Software\Microsoft\ExchangeServer\v15\EdgeTransportRole OK
RegQueryValueEx HKLM\Software\Microsoft\ExchangeServer\v15\EdgeTransportRole\ConfiguredVersion == 15.2.1118.7  OK


The hub transport role is most likely missing in the edge transport server but the counter should be available in the performance monitor tool.
If the counters: "submission queue length " and the "unreachable queue length" are present in the Windows performance monitor tool the following actions should be taken. 


In the Edge server's exchange_monitor configuration file add the "edge" role to the roles key for the <Unreachable Queue Length-Transport> and for the <Submission Queue Length> sections:

Examples below: 


<Unreachable Queue Length-Transport>
         met_id = 3.1.12:71
         active = yes
         description = Unreachable Queue Length is the number of items in the unreachable queues.
         object = MSExchangeTransport Queues
         counter = Unreachable Queue Length
         x_instance = _total
         alarm_limit = 100
         alarm_required = yes
         cmp_type = gt
         group = Transport Role
         qos = yes
         alarm = no
         short_unit = msgs
         long_unit = messages
         roles = hub,edge
         message_on_alarm = 
         message_on_clear = 
         servers = 2010,2013,2016,2019
      </Unreachable Queue Length-Transport>



   <Submission Queue Length>
         met_id = 3.1.12:43
         active = yes
         description = Shows the number of messages in the submission queue.
         object = MSExchangeTransport Queues
         counter = Submission Queue Length
         alarm_limit = 150
         alarm_required = yes
         cmp_type = ge
         group = Transport Role
         qos = yes
         alarm = yes
         short_unit = msgs
         long_unit = Number of Messages
         servers = 2010,2013,2016,2019
        roles = hub,edge
         message_on_alarm = PerformanceValueExceedsLimit
         message_on_clear = PerformanceValueClear
         instance = _total
         max_samples = 1
         excludes = 
      </Submission Queue Length>



Note: there are 2 sections for  "Unreachable Queue Length-Transport". One for refers servers = 2007" and an other one for the other Exchange supported versions. Update the relevant section. In this case the relevant sections is the the ones that refer to "servers = 2010,2013,2016,2019" as in the example above.