maiolv.blogg.se - Allmänt

Add-Content -Path $PluginDocFile -Value '| Argument | Throws error on | Ok range |'.

Add-Content -Path $PluginDocFile -Value ''.

Most of the plugins allow the usage of default Icinga threshold range handling, which is defined as follows:'

Add-Content -Path $PluginDocFile -Value 'Below you will find a documentation for every single available plugin provided by this repository.

The plugins support all other threshold ranges as well: If you want the check to be ok when 1 process is found and critical if less than one (no processes) are found the threshold for critical should be 1: If you run the check with the processname “outlook” (which is not running) or the real name from the task manger - the threshold values are the base value from the check - the check result is always 0 (OK) But at my first tests the result was diffrent: We wanted to give Invoke-IcingaCheckProcessCount a chance and expected a similar behavior like check_procs command on linux from the monitoring-plugins. The service can still running but the process could be killed for some reason.Īs noted in old threads the check_procs.exe only counts the process. The background is - as you can imagine - that some services are starting some processes like Java. One of the new requirements is to monitor processes also next to the windows services. This means that SCOM can be completely replaced on some servers.īefore we start to write our own scripts we want to use what already exists like the checks icinga installs automaticallyor the new icinga-powershell-plugins.

Successively we get more and more requirement besides to some base checks (like cpu, memory, disk) to monitor more and more. Our windows server admins installed the last weeks the Icinga agents on our windows servers (very often instead or parallel to SCOM).