Forum Discussion
Write time latency is higher than read time latency
Few days ago we connected our Exchange servers to our monitoring system (Zabbix). Short after this we received lots alerts about write time latency is higher than read time latency for all databa...
This is just Zabbix being Zabbix. I assume you are using default template for Microsoft Exchange by Zabbix.
I've seen this recently on one of my brand-new Exchange deployments.
Trigger works like this: If Average (Database Writes Latency) > Average (Database Reads Latency), then throw warning.
The thing is when database is inactive or empty, read latency and write latency are close to 0. But I still have DAG replication, that's why there is some activity on disk. Sometimes I got 0.000015ms for read latency and 0.00002ms for write latency.
Technically Zabbix is right. Write latency is greater then read latency, but it doesn't make sense in my case. The numbers are insignificant.
I've seen this recently on one of my brand-new Exchange deployments.
Trigger works like this: If Average (Database Writes Latency) > Average (Database Reads Latency), then throw warning.
The thing is when database is inactive or empty, read latency and write latency are close to 0. But I still have DAG replication, that's why there is some activity on disk. Sometimes I got 0.000015ms for read latency and 0.00002ms for write latency.
Technically Zabbix is right. Write latency is greater then read latency, but it doesn't make sense in my case. The numbers are insignificant.