bfenda

I do also agree with the previous posts. I would expect the overall cpu to be the average of all sockets, as this tends to conflict with a single threshold...

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....

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?

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....

Hello @LordHepipud, Not exactly the same cmdlet. Here is what we do in our case: ``` Register-IcingaBackgroundDaemon -Command 'Start-IcingaServiceCheckDaemon' Register-IcingaServiceCheck -CheckCommand 'Invoke-IcingaCheckCpu' -Interval 300 -TimeIndexes 5m, 15m Disable-IcingaAgentFeature -Feature mainlog...

Hi @LordHepipud, I just double checked your changes. In my case the ForceExecution will never be true as the get-icingacachedata does not return anything.

Hi together, I would also add to it. Since updating to 2.14.3 especially we see various checks on Icinga Agents, frequently run into timeouts. The Timeout is set to 60...

@LordHepipud I will update to 1.13.3 once it is released. Based on the milestone it shouldn't be to far off. I will give you feedback once I released it in...

Hey together, I am expierencing a similiar issue since upgrading to 1.13.0 using the IcingaAgentInstall Wizard:  What I also found is. If I start a new Powershell session after...

Hi @LordHepipud, Not excactly sure if that's case for the opening of this thread. I had the same issue for the last month. Especially for some Citrix Management host the...