Systemd Service summary issues with check_mk

I’m getting alot of event noise caused by systemd summarty seeing check_mk either activating or deactivating. I’ve tried disabling via filter the service check_mk@* and the message slightly changed but I still bounce between critical and ok . I’m thinking there should be a timer to ignore things activating or deactivating within the last check period multiple. In this case it’s just a timing bug where systemd status is gathered and captures the check_mk.socket service in it’s transient state. Any other Ideas on how to clean this up ?

(after filtering check_mk@ service from systemd summary)

CRIT - 110 services in total, 1 static service deactivating (user@0) CRIT , 1 ignored services, 4 disabled services
OK - 109 services in total, 1 ignored services, 4 disabled services
CRIT - 110 services in total, 1 static service deactivating (user@0) CRIT , 1 ignored services, 4 disabled services
OK - 109 services in total, 1 ignored services, 4 disabled services
CRIT - 110 services in total, 1 static service deactivating (user@0) CRIT , 1 ignored services, 4 disabled services

(before filtering check_mk@ service from systemd summary)
OK - 109 services in total, Service ‘check_mk@8168-10.62.8.100:6556-10.62.48.110:38070’ activating for: 0.00 s, 4 disabled services
CRIT - 110 services in total, 1 static service deactivating (user@0) CRIT , Service ‘check_mk@8166-10.62.8.100:6556-10.62.48.110:35670’ activating for: 0.00 s, 4 disabled services
OK - 110 services in total, Service ‘check_mk@8165-10.62.8.100:6556-10.62.48.110:34426’ activating for: 0.00 s, 4 disabled services
CRIT - 110 services in total, 1 static service deactivating (user@0) CRIT , Service ‘check_mk@8163-10.62.8.100:6556-10.62.48.110:60350’ activating for: 0.00 s, 4 disabled services
OK - 109 services in total, Service ‘check_mk@8158-10.62.8.100:6556-10.62.48.110:54316’ activating for: 0.00 s, 4 disabled services

The service triggering the CRIT isn’t check_mk@… but user@0.
I suggest filtering out user@\d+ instead of check_mk@.

Btw, your regex isn’t what you think it is (but matches anyway). check_mk@* means check_mk followed by an arbitrary number of @ characters (including none). It matches check_mk and check_mk@@@@@@hello and check_mkhello. Since the regexes match at the beginning you can simply write check_mk@ (or check_mk@.*).