Discussion thread for official Zabbix Template Microsoft Exchange

[AlexL]

This thread is designed to provide grounds for discussion of the official Zabbix Template for Microsoft Exchange.
The template and details of the template soon will be available in git repository.


Zabbix is always looking for ways to improve our services and to make our users happier.
We pride ourselves on doing our best each and every day, but we know that there is always something more to learn.
We would like to hear back from you to know what have you liked and what would you improve in the template.

[chojin]

This template can't be linked to a host which already has the OS Windows by Zabbix Agent template assigned due to

Discovery rule "service.discovery" already exists on "host", inherited from another template.

And as Exchange runs on a Windows server, the chance is big that the host already has the Windows OS template linked.

I assume this can be solved by adding a "virtual" host in zabbix, only for the Exchange application, but I assume that won't be a feasible solution for many users?
Another workaround I see is adding an alias service.discovery[*] to the agent and setting the item key of the Exchange discovery to "service.discovery[exchange]". But then there probably will be duplicate services as those services will be discovered by both the OS template and this template, so the host will have to get some macro's for the OS service discovery to filter out the exchange services. This macro can probably be defined in this template, but I'm not sure if that will work as the OS template is not a linked template to this one so I'm not sure about the macro inheritance..

[chojin]

Also the current template filters on {#SERVICE.STARTUP} matches "{0"
This should be "0" without the "{"

[rodikov]

Please add database size monitoring to the template.

Example:
Item prototypes name: {#EDB.NAME} edb file size
Item prototypes key: vfs.file.size[{#EDB.PATH}]
Type of information: Numeric (unsigned)
Units: B

At the moment, I get the path to the database using PowerShell:
$edbList = Get-MailboxDatabase
foreach ($edb in $edbList) {
@{
"{#EDB.PATH}" = $edb.EdbFilePath.PathName
}
}


I would like to get this in the official template.

[rodikov]

Also ask to add monitoring of mail queues.
Example:
perf_counter_en["\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length"].last(0)}>100
perf_counter_en["\MSExchangeTransport Queues(_total)\Active Non-Smtp Delivery Queue Length"].last(0)}>100
perf_counter_en["\MSExchangeTransport Queues(_total)\Active Remote Delivery Queue Length"].last(0)}>100
perf_counter_en["\MSExchangeTransport Queues(_total)\Aggregate Delivery Queue Length (All Queues)"].last(0)}>3000
perf_counter_en["\MSExchangeTransport Queues(_total)\Largest Delivery Queue Length"].last(0)}>100
perf_counter_en["\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length"].last(0)}<>0
perf_counter_en["\MSExchangeTransport Queues(_total)\Retry Mailbox Delivery Queue Length"].last(0)}>100
perf_counter_en["\MSExchangeTransport Queues(_total)\Retry Remote Delivery Queue Length"].last(0)}>50
perf_counter_en["\MSExchangeTransport Queues(_total)\Submission Queue Length"].last(0)}>50
perf_counter_en["\MSExchangeTransport Queues(_total)\Unreachable Queue Length"].last(0)}>50

[Ahmed UĞUR]

Hello, I imported "Microsoft Exchange Server 2016 By Zabbix Agent" template in our Zabbix server but doesn't seem all items, triggers and graphs. I saw just 9 items, 0 Trigger and 1 Graph. There is no error when imported. When I try create item or trigger manually, Zabbix tell me already exist trigger in "Microsoft Exchange Server 2016 By Zabbix Agent" but I cannot see. I use Zabbix 6.0.10

[powerman2003]

Hello! Have some trouble. Have two exchange. exch2 work fine. exch1 dont discover database.
different exch1 & exch2 is language. exch1 have russian language, exch2 have english. No more different.

[Jeriho]

Hello everybody!
There is a mistake in this template, that prevents it from functioning properly on localized or two and more language installs of WIndows (or maybe even on single-language english Windows too).
Database discovery rule key at line 118 must be fixed:
WRONG line:
          key: 'perf_instance.discovery["MSExchange Active Manager"]'
RIGHT line:
          key: 'perf_instance_en.discovery["MSExchange Active Manager"]'

Otherwise database discovery doesn`t work, and becomes "unsupported". After fix it works pretty good on localized and english versions of windows 2022 + Exchange 2019