Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Invoke-IcingaCheckProcessRunning.psm1 #3

Closed
wants to merge 1 commit into from

Conversation

DoktorAerzt
Copy link
Contributor

I wasn´t sure to create one or 2 pr for the plugins.

This plugin checks if a process is running or not and will return OK or CRITICAL

@LordHepipud
Copy link
Collaborator

Thank you for your contribution ! Was there a specific reason on why you are not using the Invoke-IcingaCheckProcessCount plugin?

As far as I understand both are doing the same thing - or am I mistaken here?

@DoktorAerzt
Copy link
Contributor Author

The point is, if i unterstand Invoke-IcingaCheckProcessCount correct, you only can check how many processes are running and get a warning or critical when to many are running.

Invoke-IcingaCheckProcessRunning checks if a process is running and you get an critical if it is not running.

I think one solution whould be to negate Invoke-IcingaCheckProcessCount

@LordHepipud
Copy link
Collaborator

LordHepipud commented Nov 18, 2019

You could already do that, because the Process Check Plugin is following the Icinga / Nagios Development Guides for Thresholds. To check if a process is running, the command would look like this

Invoke-IcingaCheckProcessCount -Process Firefox -Critical '1:'

Output

[CRITICAL] Check package "Process Check" - [CRITICAL] Process Count "Firefox"
\_ [CRITICAL] Process Count "Firefox": Value "0" is lower than threshold "1"
| 'process_count_firefox'=0;;1:

Does this help you and matches your requirements?

@DoktorAerzt
Copy link
Contributor Author

Perfect that was exactly what i want.
I close this pr.

@LordHepipud
Copy link
Collaborator

Allright - Thank you. I will extend the documentation on that a little more, to ensure everyone will be aware of this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants