Closed K0nne closed 2 years ago
Hello @LordHepipud Could you please provide a PR?
Hello, can you please test the linked PR @K0nne ?
Thanks for the PR. I will report back on tuesday.
Hello!
I tested the PR. It fixed the problem only for the overcommitment check.
before:
after:
From what I see, the overcommitment check has 3 sub sections, from which were 2 ok before.
The other 2 checks only have 1 sub section, which is still unknown. maybe there's a connection.
Have you used the argument -AvoidEmptyCheck
for snapshots and switches?
I would not want to add this as default behavior, as it might be a real problem on certain machines, unlike the overcommitment check.
I forgot to update the command bundle. Now the fix ist working as intended :)
How are the tests going? Can we merge the PR or are any other issues remaining? I assume #48 is working as expected now?
The checks are working fine now. Thanks a lot! You can merge it.
We had to add the Monitoring-User to "Hyper-V Administrators". After a restart of the "Icinga2" Service the checks are working as expected.
Maybe #40 whould be nice :)
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.
The following checks are affected:
Invoke-IcingaCheckHyperVSnapshot
Invoke-IcingaCheckHyperVVirtualSwitches
Possible Solution
Add a parameter to toggle the behaviour between OK and UNKNOWN.
Context
This ist a continuation of https://github.com/Icinga/icinga-powershell-plugins/issues/217, because I was missinng 2 checks.