...
The plugin uses a golang-executable file (included in the plugin as send2jsm) to create, acknowledge, and close alerts in Jira Service Management. Configure Icinga to execute this file on events to create, acknowledge, and close alerts in Jira Service Management. The following table lists the parameters and states if they are mandatory.
| Expand |
|---|
| title | Configuration parameters |
|---|
|
Configuration parameter | Description | Mandatory? | Location |
|---|
apiKey | Copy the URL from the integration configuration page in Jira Service Management. send2jsm uses this key to authenticate to Jira Service Management. API key is also used to identify the right integration configuration that should be used to process alerts. | Yes | /home/jsm/jec/conf/jec-config.json | baseUrl | Change this field according to your Jira Service Management environment (For example: EU, sandbox) | No | /home/jsm/jec/conf/jec-config.json | responders | The default responder. This field is used to specify which responders should be notified for Icinga alerts. You can modify it to route alerts to different teams or schedules in Jira Service Management. This field is required if you haven’t set responders in the integration configuration page. | No | /home/jsm/jec/conf/integration.conf | tags | Tags of the alert that created in Jira Service Management. | No | /home/jsm/jec/conf/integration.conf | icinga_server | The Icinga server in Jira Service Management and only required when there are multiple Icinga servers. This is used by Jira Service Management when sending actions run by users (acknowledge, close, etc.) back to your Icinga servers via JEC. | No | /home/jsm/jec/conf/integration.conf | logPath | The full path of the log file (Default: /var/log/jec/send2jsm.log) | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.enabled | To enable or disable the external proxy configuration. Default: false | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.host | Host of the proxy | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.port | Port of the proxy | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.scheme | The proxy connection protocol. It may be http or https, depending on your proxy servers. Default: http | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.username | The username for proxy authentication | No | /home/jsm/jec/conf/integration.conf | icinga2jsm.http.proxy.password | The password for proxy authentication | No | /home/jsm/jec/conf/integration.conf |
|
Configure the golang-executable file in any of the following three methods:
...
Select the Send Alert Actions To Icinga checkbox on the integration configuration page. You can combinedly use JEC and Icinga scripts to update alerts on Icinga. With this setup, you can deploy your own script, modify the ones provided, or run customized actions on Icinga.
To run actions in ZenossIcinga, JEC gets the configuration parameters from the configuration file, config.json (found at /home/jsm/jec/conf/jec-config.json).
...