Exchange IS Client Type services becoming Unknown

[jcrow]

CMK version:1.5.0p21
OS version: CentOS 7.9

Error message: No error

Hey all,

We have Exchange 2019 running on Server 2022 being monitored.

Among the check_mk services that were first picked up are all the Exchange IS Client Type services. Examples in below screenshot.

When created, Exchange had a default database. I created two more databases and now want to remove the default one.

I moved all the arbitration/system mailboxes off the default one on to one of the new databases. To check if it is ok, I dismounted the default one. Exchange is working fine, but all those Exchange IS Client Type services became Unknown. Running an automatic refresh does not bring them back. Remounting the default database does bring the services back.

Is this known behaviour?

thanks

j

EDIT: Nevermind, I fixed the issue. Restarting the Exchange Information Store service got the services back in check_mk.

[gstolz (Gerd Stolz)]

Maybe also of relevance regarding these services:

Stale Service since 15h - FUP

also mein aktueller Stand: Der Check gegen “Exchange IS Client Type _total” funktioniert nicht, weil er auf einem Counter basiert, der entgegen aller Doku mal steigt und mal sinkt. D.h. Checkmk versucht normal zwischen Messpunkt Alt und Messpunkt Neu den Unterschied zu berechnen und diesen dann auf RPC Requests / Sekunde herunterzurechnen, das geht aber nicht, wenn der Counter sinkt, denn wenn der neue Counter niedriger als der alte ist, dann weist dies normalerweise immer auf einen Counter Ov…

or translated in english:

Stale Service since 15h - FUP