I don’t get why this is “unknown” instead of “critical” (or even better, configurable with a rule). I have a Linux server with a CIFS share permanently mounted. If it becomes unmounted, it goes to “unknown” and I don’t notify on “unknown” because there would just be too many alerts.
This is default behavior when a mount point is not found. It’s not something that only applies to CIFS mounts. If you want this to become critical, you could use a “Service state translation” rule to do so.
Hope that helps you…
Wow, this is awesome. I did not know about this rule… I have a feeling I’ll be making use of it other places.