I removed the summary rules and the nasty looking single services rules from the earlier posts but still see this check_mk@ thing as a crit after rescanning hosts.
I did find this rule so I guess I can just change the severity of the unmonitored service but if someone stood up a new service on one of my systems it would be cool to be warned about it
