Page History
Table of Contents |
---|
Introduction
JS7 - Notifications - Configuration is performed from the Configuration->Notification sub-view of the JOC Cockpit and includes setting up the configuration for the JS7 - Monitor Service.
- 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 makes use of uses the JSend NSCA Java API. Consider Note that this fragment type does not support more elaborated encryption as required by a number of System Monitors.
...
Attribute | Usage | Description |
---|---|---|
name | Required | The unique name of this fragment. |
monitor_host | Required | This setting specifies the host name or IP address of the System Monitor host. |
monitor_port | Required | This setting specifies the TCP port that the System Monitor listens to. |
monitor_password | Optional | This setting specifies the connection password
|
monitor_connection_timeout | Optional | This setting specifies the connection timeout in ms. Default: |
monitor_response_timeout | Optional | This setting specifies the response timeout in ms. |
monitor_encryption | Optional | This setting specifies that the communication with the System Monitor is encrypted. By default no encryption is used.
|
service_host | Required | This setting specifies the name of the host that executes the passive check. |
Note | ||
---|---|---|
| ||
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 - Notifications - 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. |
Examples
Nagios® / op5®
The following is an excerpt from an XML configuration for notification with Nagios® and op5® via the NSCAFragment:
Code Block | ||||
---|---|---|---|---|
| ||||
... <!-- monitor_host The hostname or IP address of the System Monitor host monitor_port The TCP port that the System Monitor listens to monitor_encryption Encryption algorithm service_host The host that executes the passive check. The name must match the corresponding setting in the System Monitor. ${MON_O_CONTROLLER_ID} The JS7 Controller ID, see Monitor Variables --> ... <Message name="nsca_message"><![CDATA[ controller id=${MON_O_CONTROLLER_ID}, history id=${MON_O_HISTORY_ID}, workflow path=${MON_O_WORKFLOW_PATH}, order id=(${MON_O_ORDER_ID}), order step status=${MON_OS_SEVERITY}, error=${MON_OS_ERROR_TEXT} ]]></Message> ... <NSCAFragment monitor_host="monitor_host" monitor_port="5667" monitor_encryption="XOR" service_host="service_host"> <MessageRef ref="nsca_message"/> </NSCAFragment> ... | ||||
Note | ||||
| ||||
In case 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 could only use the plugin in case that no encryption (type: NONE) is used. Instead, you can use the XMLCommandFragment element and indicate the exact command to send passive checks to your System Monitor from a remote machine by use of the System Monitor's Agent. |