Page History
Table of Contents |
---|
Introduction
- The NSCAFragment
...
SystemMonitorNotification / Notification / NotificationMonitor / NotificationInterface
NSCA plug-in Interface to be executed for System Monitor notification.
- is used for direct connections to System Monitors that operate a Nagios-compatible NSCA service for passive checks such as Nagios®, Icinga®, Opsview®.
- This fragment type makes use of the JSend NSCA Java API. Consider that this fragment type does not support more elaborated encryption as required by a number of System Monitors.
NSCAFragment
NSCAFragment
supports NotificationInterface
supports the following attributes:
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. |
plugin
Default:
JobScheduler releases before 1.11com.sos.scheduler.notification.plugins.notifier.SystemNotifierSendNscaPlugin
JobScheduler releases starting from 1.11
com.sos.jitl.notification.plugins.notifier.SystemNotifierSendNscaPlugin
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
... <NotificationInterface<Message monitor_hostname="monitor_host" monitor_port="5667" monitor_encryption="XOR" service_host="service_host"nsca_message"><![CDATA[ schedulercontroller id=${MON_NO_SCHEDULERCONTROLLER_ID}, history id=${MON_N_ORDERO_HISTORY_ID}, job_chainworkflow path=${MON_NO_JOBWORKFLOW_CHAIN_NAME}PATH}, order id=(${MON_NO_ORDER_ID}), order step status=${MON_N_ORDER_STEP_STATEOS_SEVERITY}, error=${MON_NOS_ERROR_TEXT} ]]></NotificationInterface>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 it the plugin in case you use that no encryption (type: NONE) for connections to Opsview®is used. Instead, you should can use the XML |