...
| Expand |
|---|
| title | Method 2: Configure by using Golang flags |
|---|
|
Configure by entering flags into the command of the notification created in Icinga, as described earlier in this section. Use -apiKey flag for your apiKey. To send additional custom arguments, add them after the flags. For example, customArgName1 customArgValue1 customArgName2 customArgValue2. Parse custom arguments by adding {{_payload.customArgName}} to wherever is needed in the input fields. To learn more about using raw parameters, see dynamic fields. |
| Expand |
|---|
| title | Method 3: Configure from script |
|---|
|
Configure apiKey from the send2jsm.go script. Build the script again and put the new executable into the /home/jsm/jec/scripts directory. Learn more about the location of the send2jsm.go and how to build a go script in the “Source and recompiling send2jsm” section in this article. |
...
| Info |
|---|
The Icinga integration package does not support SSL v1.0. If your Icinga Server has SSL v1.0, upgrade your SSL server. |
Source for and recompiling send2jsm
The source for the executable send2jsm is found in /usr/bin/ and send2jsm.go, in /home/jsm/jec/scripts respectively, and is also available in this repository. To change the behavior of the executable, edit send2jsm.go and build it by using the following command: go build send2jsm.go
...
| Expand |
|---|
| title | 1. Icinga alerts are not getting created in Jira Service Management |
|---|
|
Run the following test command from the shell and check if a test alert is created in Jira Service Management: | Code Block |
|---|
/home/jsm/jec/scripts/send2jsm -entityType=host -t=PROBLEM -hs=DOWN -hn=test_host
|
If you get a "Trace/breakpoint trap" error, the send2jsm plugin isn't compatible with the server distribution. Rebuild send2jsm.go according to the specific server environment as described in the “Source for and recompiling send2jsm” section in this article. If the alert is created in Jira Service Management, the integration is configured correctly. Icinga is probably not notifying the Jira Service Management contact for alerts. Check your Icinga alert notifications log. If the alert is not created in Jira Service Management, check the logs at /var/log/jec/send2jsm.log.
Look for the following errors in the log file: If you see "RestException[Could not authenticate.]" in the logs, Jira Service Management couldn't identify the API key. Check if the API key is set correctly per the steps outlined in the “Configure the Jira Service Management plugin in Icinga” section of this article. If unsure of the problem, set the plugin's log level to debug and try again. Contact us and share the logs.
If there is no /var/log/jec/send2jsm.log file or there are no logs in it, check the following: Check if the Icinga user has permission to write to /var/log/jec directory. The installation package should automatically do this for you. If you face issues, run the following command:
chown -R icinga:jsm /var/log/jec Check the Icinga server logs at /opt/icinga/log/zeneventd.log. See if there are error logs regarding send2jsm. Contact us with the logs as needed.
Set send2jsm plugin's log level to DEBUGSet the send2jsm plugin's log level to DEBUG. Open the /home/jsm/jec/conf/integration.conffile and change the line send2jsm.logger=warning to icinga2jsm.logger=debug. |
| Expand |
|---|
| title | 2. The Icinga alert is not acknowledged when the alert is acknowledged in Jira Service Management |
|---|
|
Check the activity log. If "Posted [Acknowledge] action to Icinga.." is not present in the log, Jira Service Management didn't send the Acknowledge action to Icinga. Check the integration configuration, it might not have a matching the alert action. If only the "Posted [Acknowledge] action to Icinga.." log occurs followed by no related logs, it might mean JEC is having connection problems. Check the logs.
Learn more about activity logs. |
...