Icinga / Icinga/icinga-powershell-plugins

Invoke-IcingaCheckCPU: Icinga Plugin execution error was thrown during API request: Attempted to divide by zero.

Open
#489 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
55
Forks
30
PR merge metrics
No merged PRs in 30d

Description

This UNKNOWN-event appeared after the last reboot of the Win-2016-Server, I've never seen this anywhere else in our environment.
The output of the plugin itself looks good:

PS C:\> Invoke-IcingaCheckCPU -Core Total -Critical 99 -Limit100Percent -OverallOnly -Verbosity 2
[OK] CPU Load
\_ [OK] Overall Load: 10.03480%
\_ [INFO] Socket #0
   \_ [INFO] Core Total: 7.03596%
\_ [INFO] Socket #1
   \_ [INFO] Core Total: 13.03364%
| totalload::ifw_cpu::load=10.03480%;;99;0;100 0_total::ifw_cpu::load=7.03596%;;;0;100 1_total::ifw_cpu::load=13.03364%;
;;0;100
0

It is the only icinga-service on this server which shows this behaviour.
I already refreshed/rebuilt the cache, restarted IfW etc. - nothing changed.

Component    Version
---          ---
agent        2.16.5
framework    1.15.0
plugins      1.15.0
service      1.3.0

no JEA enabled

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the request using Invoke-IcingaCheckCPU with the reported arguments on the affected Windows Server environment, then inspect that entry point for the divide-by-zero path. Compare the successful plugin output with the failing API request and determine what condition triggers the UNKNOWN event. Done means the request no longer throws the error and the behavior is covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.