Before configuring things, it's useful to think through the setup, and doubly so with IT services. A large service tree might look impressive, but it might not represent the actual functionality well and might even obscure the real system state.
Disk space being low is important, but it doesn't actually bring the system down; it doesn't affect the SLA. The best approach likely would be to only include specific checks that identify a service being available or operating in an acceptable manner; for example, the SLA might require some performance level to be maintained. Unless we want to have a large, complicated IT service tree, we should identify key factors in delivering the service and monitor those.
What are the key factors? If the service is simple enough and can be tested easily, we could have a direct test. Maybe the SLA requires...