Feature: Please add a possibility to mitigate the checkresult from "unknown" to "ok" if no checks could be added to a package

[K0nne]

Expected Behavior

I whould love to have a way to mitigate the checkresult to "OK" if a check can not be added to the package.

Current Behavior

I have a few hyper-v checks, which sometimes go "unknown", because the things to check are currently not available. In my case this is not necessary a problem.

Example: The perfcounters to check are only available if client vms exist at the host

Example: Overcommitment is not used

Possible Solution

Add a parameter to toggle the behaviour between OK and UNKNOWN.

Context

If the hyperv hosts have no client vms (e.g. a new cluster or hosts in maintenance) the "unknown" distracts the users.

[LordHepipud]

Thank you for the issue. This is not a feature request, but a bug. This package should never throw unknown in case no packages are configured.
I assume there are no machines on this system configured?

Sidenote: For the Performance counters I will add a flag to configure it. Should have read the entire issue :D

[K0nne]

Yes, this is a new cluster. The hosts currently have no client VMs configured.

[LordHepipud]

Fixed the overcommitment in; Icinga/icinga-powershell-hyperv#41

[K0nne]

We are going to test this tomorrow.
Unfortunately the hyperv checks Invoke-IcingaCheckHyperVSnapshot and Invoke-IcingaCheckHyperVVirtualSwitches are also affected:

[UNKNOWN] VM Snapshots: No checks added to this package

[UNKNOWN] Virtual Switches: No checks added to this package

[LordHepipud]

Could you please open a new issue on the Hyper-V repository for this? A simple Copy&Paste would be enough.

I will provide a PR for this day.

Thank you in advance!