When one of these exit codes is received the appropriate dynamic evidence table structure is created and all further exit codes are handled correctly.
NAGIOS WINDOWS MONITOR CODE
To correctly create this component monitor, you must first return an exit code which results in an Up (0), Warning (2), or Critical (3) status. The following table shows a list of valid return codes, along with their corresponding service or host states. Nagios determines the status of a host or service by evaluating the return code. Scripts must report status through return codes Use the Orion Service Manager to restart all services.Modify algorithms in that section, as necessary.In a text editor, open .config and locate the following section:.Create a backup copy of the .config file.On the Orion server, navigate to this default folder: c:\Program Files (x86)\SolarWinds\Orion\APM.Contact Technical Support for assistance, if necessary.Ĭhanging algorithms can have security implications in some environments. If key exchange algorithms cause high CPU usage by Job Engine Workers processes, you can reorder or remove algorithms to resolve issues. This component monitor uses SSH to connect to target systems. To override the default description, add to or replace existing text. Field descriptionsĪ default description of the monitor. If that occurs, try adjusting algorithms to reduce CPU usage, as described in Troubleshoot high CPU usage.Ĭhanging key exchange algorithms can have security implications in some environments. If key exchange algorithms cause high CPU usage due to the number of active Job Engine Workers processes, you may notice gaps in polling data and slow responses from the Orion Web Console. Like the Linux/Unix Script Monitor, the Nagios Script Monitor uses SSH to connect to target systems. Adding a script that use python $(SCRIPT) as the Script Argument.Deploying agents to monitored target nodes, and.Review Configure Linux/Unix systems for the Orion agent for Linux and set up target systems, which involves: Agentless monitoring does not require credentials. To use the Orion agent for Linux, include credentials with permission to run scripts on target systems. For details, see Write scripts for SAM script monitors. If you exceed the maximum allowed, remove the excess output pairs or they will be ignored. For reference, see Nagios Plugin API (© 2021 Nagios Enterprises, available at, obtained on June 22, 2021).Ī maximum of 10 output pairs can be returned. This component monitor can return multiple results and process the Nagios output.
The statistic for this component monitor is the value returned by the script. Sample scripts are provided in this default folder on the Orion server: C:\Program Files (x86)\SolarWinds\Orion\APM\SampleScriptMonitors Nagios scripting in SAM component monitors.To learn about creating custom scripts with this monitor, see these topics in the SAM Custom Template Guide: This SAM component monitor uses SSH to upload a Nagios script to a Linux/Unix server, runs the Nagios script on the server and then processes the script's exit code and text output.