-
Home
- Studio Monitors with Content 11
Nagios Plugin
The purpose of the Nagios Plugin Monitor is to execute any Nagios Plugin and monitor the results directly from TrueSight without requiring a native Nagios environment.
To be able to execute a specific Nagios Plugin, Monitoring Studio X simply needs the command to run the Nagios plugin. You can either enter manually the command or refer to an embedded file using the %{FILE:<filename>}
macro. Refer to Embedded Files for more details.
You can choose to run the Nagios plugin on the agent system, or on the monitored system (remotely).
The Nagios Plugin Monitor supports the %{PASSWORD}
macro, which will be replaced at run-time with the password of the selected credentials. User-defined %{...PASSWORD}
macros will also be replaced with the decrypted password.
Nagios plugins that provide performance information are fully supported. Each output line of the Nagios plugin will be represented with a separate instance in TrueSight, with its own metrics.
Refer to the table below to know how to configure the properties available:
Property | Description |
---|---|
Nagios Plugin Command | Full path to the Nagios Plugin Command with options to be run (Example: /usr/local/nagios/libexec/check_disk -w 30% -c 50% ). You can use the %{HOSTNAME} ,%{USERNAME} and %{PASSWORD} macros if the command is run on the Agent system. When monitoring remote Windows system from a PATROL Agent running on a UNIX/Linux system, the command will be supported only on the Agent system. Example: /usr/local/nagios/libexec/check_nt -H $HOSTADDRESS -v CPULOAD -w 80% -c 90% . Here the macro $HOSTADDRESS will be resolved to the monitored host at the time of execution. |
Execute as | (Only when command is run on the host) Credentials required to execute the command. By default, System Credentials are used. |
Set %{USERNAME} And %{PASSWORD} With | (Only when command is run on the Agent) Credentials available through the %{USERNAME} and %{PASSWORD} macros in the command executed on the Agent. The command will be executed as the default PATROL Agent user. |
Run this Command on the Monitored Host or Agent system? | (Not available when command is run from UNIX/Linux Agent to Windows system) Host on which the command will be run (HOST or AGENT). When the command is run on the Agent, you will have to set the credentials to be used through the %{USERNAME} and %{PASSWORD} macros. |
Display Name | Name to identify the Nagios Plugin instance in TrueSight Operations Management. |
Internal ID | ID to be used to store the Nagios Plugin Monitor configuration in the PATROL Agent configuration. This Internal ID is automatically generated based on the Display Name provided but can be edited if needed. |
Collect Schedule | How often new data is collected. A new collect can be performed from once every second, to once in a day. By default, the collect schedule is set to 2 minutes. |
Timeout After | Time in seconds after which the command will be stopped (Default: 30 seconds). If the timeout is reached, a new error is logged in the Collection Error Count parameter of the template, indicating that the command failed to execute |
Report Unknown (3) Service Status | How an unknown error will be reported in TrueSight. |
Extract Nagios Performance Data | When enabled (ON), performance data provided by the Nagios plugin will be extracted and displayed in separate instances. |
Use Plugin's Default Alert Thresholds on Value | When enabled (ON), the default alerts for the Value attribute based on the returned performance data will be used. |
Rescaling | How Monitoring Studio X will rescale the extracted value. |
What to Do with Transient Instances | How Monitoring Studio X will handle transient instances. |
For more information about the parameters available and the thresholds set by default, refer to Studio Nagios Plugin and Studio Nagios Performance Data.
Refer to Alert Messages and Actions to know how to configure alerts on parameters.