Home Directory Plugins Operating Systems Windows Check multiple windows processes dotnet core

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

Check multiple windows processes dotnet core

Rating
0 votes
Favoured:
0
Current Version
3.0
Last Release Date
2023-12-15
Compatible With
  • Nagios 4.x
License
Other
Hits
1122
Files:
FileDescription
check_win_processes_dotnetcorecheck_win_processes_dotnetcore
Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
This is the code by David Ligeret from the 'Check multiple Windows Processes v2' SNMP process check that exists on this site with added features to monitor a dotnet.exe instance and the ability to require more than 1 instance of a process (list it more than once).
This is the code by David Ligeret from the 'Check multiple Windows Processes v2' SNMP process check that exists on this site. It works the same but with some added features. You can specify the same program name twice or more to expect more than 1 running. I also added the ability to specify dotnet.exe,someapp.dll so that you can check if a specific dotnet core app is running based on the parameter of dotnet.exe. This is based on detecting dotnet.exe as a program name and then querying for the SNMP parameters of the exe to see what DLL is being called by dotnet. the ',' is used for the parameter delimiter when specifying the dll name for dotnet.exe.

An example... process1.exe process2.exe dotnet.exe,someapp.dll process2.exe

This would require 1 process1.exe to be running, two process2.exe to be running and 1 dotnet.exe to be running with the text someapp.dll as a part of the parameter that dotnet.exe is calling.