ThresholdInterval not working with Framework 1.13.2

[geotekberlin]

The ThresholdInterval option fails on Invoke-IcingaCheckCPU commands on a fresh Powershell 1.13.2 Framework installation with 1.13 Plugins on a Windows Server 2016 host. Only the CheckCPU command fails, all other check commands work as expected.

I have read here that metrics over time are no longer written but monitoring by using the "-ThresholdInterval" argument is still possible.

TestIcingaForWindows shows the following result:

The shown errors are expected since we are not using the Icinga Service.

Any help would be appreciated.

[LordHepipud]

Hello

Thank you for the issue. If the Icinga for Windows service is not installed, you cannot use the Metrics over Time feature, as it requires the Icinga for Windows service to run checks frequently on the background and calculate the averages for the defined time frames.

[geotekberlin]

I installed the Icinga for Windows service, but the error remains:
[Failed to parse metrics over time with -ThresholdInterval "5m": No data found matching the requested time index. Available indexes: []]

Configuring REST-API doesn't help either, and Icinga for Windows appears to be healthy:

I just confirmed this issue on another freshly installed Host. Is there any documentation what is needed to keep IcingaCheckCPU working in Framework 1.131.2?

[bfenda]

Hi @LordHepipud,

I noticed a similiar Issue when I upgrade from Framework 1.12.3 to 1.13.2. When installing the first Check cannot get the Threshold Interval because the index is missing. We configured the Background Daemon to run every 5 minutes.

After 5 Minutes the indizes are added and the Check is in OK State again. From my view it seems, that in previous Versions the Background Daemon executed the checks right away when started. Since 1.13.2 it seems, that you have to wait the Check interval until the first Check is executed.

best regards,
Brian

[LordHepipud]

Hello

Thank you for the input. This makes sense, as you are correct - the new implementation is waiting for the interval to pass before running a check.
We will add a "force check" as fix, in case no data is present after the daemon starts to resolve this.

Thanks for the feedback!

[bfenda]

Hi @LordHepipud,

Thank you for the contribution. A little question from my side. The milestones for 1.13.3 seems complete. Do you have an estimated date for the release?

[LordHepipud]

Heya, we are planing to release the new version this week. We are still running some tests to ensure the new version did not introduce other bugs, but are confident that everything will go smoothly.
if nothing goes wrong, you can expect a release on Thursday at latest.

[geotekberlin]

With the new plugins and framework the error still persists:

[UNKNOWN] CPU Load [UNKNOWN] Overall Load, Socket #0 (All must be [OK])
\_ [UNKNOWN] Overall Load: [Failed to parse metrics over time with -ThresholdInterval "5m": No data found matching the requested time index. Available indexes: []]

However, Use-Icinga; Invoke-IcingaCheckCPU; executed in a PS window returns meaningful values.

These are the versions involved:

agent        2.14.5    2.14.5
framework    1.13.3    1.13.3
plugins      1.13.1    1.13.1
service      1.3.0     1.3.0

Only the CPU check is affected, all other PS-Checks work fine.

Please advise.

[bfenda]

Hi @LordHepipud,
Thanks for the afford here. I have to agree with @geotekberlin. The issue does still remain. At least in the way that we use the background daemon currently.

Local Execution of invoke-icingacheckcpu with thresholdinterval does return a correct result. However as stated, there seems to be a problem in combination with Icinga.

For full measure this is the relevant path we use in the command.

Exit-IcingaExecutePlugin -Command '''Invoke-IcingaCheckCPU''' ' '-DisableProcessList' '-Warning' '80%' '-Critical' '90%' '-Core' '_Total' '-Verbosity' '2' '-ThresholdInterval' '15m'

Which results in the Unknown State because the index is not found. The Background daemon is set up like this.

Register-IcingaBackgroundDaemon -Command 'Start-IcingaServiceCheckDaemon'
Register-IcingaServiceCheck -CheckCommand 'Invoke-IcingaCheckCpu' -Interval 300 -TimeIndexes 5m, 15m

Maybe it's just a handling issue. If we should switch the way that the background daemon is initialized, you can let me know and I will try to test it out.

best regards,
Brian