search

Icinga / icinga-powershell-framework

This PowerShell module will allow to fetch data from Windows hosts and use them for inventory and monitoring solutions. Together with the Icinga Web 2 module, a detailed overview of your Windows infrastructure will be drawn.
MIT License
74 stars 33 forks source link

The check output is somewhat confusing #704

Open granatelbart opened 5 months ago

granatelbart commented 5 months ago

Hello all,

i update my icinga and icingaweb to the newest version.

Framework 1.11.1 Plugin 1.11.1 Hyper-V 1.3.0 cluster-1.3.0

2024-03-26 23_55_12-Zustand __ Icinga Web – Mozilla Firefox

I have various problems.

  1. if i run Invoke-IcingaCheckUNCPath powershell crashed
  2. just on one Hyper-v I have problems with HyperVOverCommitment. The check output is somewhat confusing. 2024-03-27 00_00_22-HyperVOverCommitment auf DATHSDHV04 DHV CLUSTER __ Icinga Web – Mozilla Firefox

I allready reinstalled the icinga and removed it from icinga-director but it didn't make a difference.

granatelbart commented 5 months ago

Before I forget, I've transitioned to IcingaDB.

oxzi commented 5 months ago

Thanks for reporting your issue.

First, is this related to Icinga DB? Did the check previously worked with IDO and how does the check's output look in Icinga Web 2 under the monitoring module?

Based on the provided screenshots, I would guess there's something wrong with your check configuration. This issue looks somewhat similar to https://github.com/Icinga/icinga-powershell-framework/issues/684.

granatelbart commented 5 months ago

IcingaDB is actually running, but IDO is experiencing the same issue.

I don't think the check-config is the problem. I have 6 Hyper-V servers running, and one of them is experiencing the issue.

Today, I encountered the same problem with disk health checks on 4 machines. After restarting the Icinga framework, everything worked fine again.

LordHepipud commented 5 months ago

Thank you for the issue. This should be resolved with v1.12.0, as we made an update to the internal checker core which now properly interprets the difference between 0 and null while working with units.

The update of the Framework would be enough for the fix to apply, in case the cause is like I mentioned,