- The NSCAFragment is used for direct connections to System Monitors that operate a Nagios-compatible NSCA service for passive checks such as Nagios®, Icinga®, Opsview®. Messages to a System Monitor can be parameterized from JS7 - Notification - Configuration, Monitor Variables.
- This fragment type uses the JSend NSCA Java API. Note that this fragment type does not support more elaborated encryption as required by a number of System Monitors.
NSCAFragment supports the following attributes:
|Required||The unique name of this fragment.|
|Required||This setting specifies the host name or IP address of the System Monitor host.|
|Required||This setting specifies the TCP port that the System Monitor listens to.|
This setting specifies the connection password
This setting specifies the connection timeout in ms.
|Optional||This setting specifies the response timeout in ms.|
This setting specifies that the communication with the System Monitor is encrypted. By default no encryption is used.
|Required||This setting specifies the name of the host that executes the passive check.|
System Monitor: Opsview
If you are using Opsview® as a monitoring tool: consider that the plugin will not work, since Opsview® supports ca. 20 encryption types that are not supported by this plugin. You can only use the plugin when no encryption (type: NONE) is used.
Instead, you can use the JS7 - Notification - Configuration Element CommandFragment and indicate the exact command to send passive checks to your System Monitor from a remote machine using the System Monitor's Agent.
Nagios® / op5®
The following is an excerpt from an XML configuration for notification with Nagios® and op5® via the NSCAFragment: