atlassian / atlassian/jsm-integration-scripts
Zabbix API Error: Invalid Parameter 'auth' When Acknowledging Alerts from JSM
- Dominant language
- Python
- Stars
- 17
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Since Zabbix version 6.2, the Zabbix API requires an API token for authentication instead of a username and password. When acknowledging an alert from JIRA, the message is sent back to the Zabbix server, but the following error is returned:
`DEBUG:root:Zabbix response: {'jsonrpc': '2.0', 'error': {'code': -32600, 'message': 'Invalid request.', 'data': 'Invalid parameter "/": unexpected parameter "auth".'}, 'id': 1}`
**Steps to Reproduce:**
- Trigger an alert from Zabbix
- Acknowledge the created alert on JSM
**Expected Result:** The acknowledgment should be reflected in Zabbix.
**Actual Result:** The error message above is returned in the output.txt file, and the acknowledgment is not reflected in Zabbix.
**Additional Information:**
Zabbix version: 7.2.4
Script set in jec-config.json: jec_action_executor_for_zabbix6.py also tested with jec_action_executor_for_zabbix4.py
jsm-integration-script version: zabbix-1.0.3_jec-1.0.5
Contributor guide
Research direction
Start with jec_action_executor_for_zabbix6.py and compare it with jec_action_executor_for_zabbix4.py, using jec-config.json to confirm which script is active. Reproduce the acknowledgment flow from JSM with Zabbix 7.2.4 and inspect output.txt and the Zabbix response. Done means acknowledging an alert in JSM is reflected in Zabbix without the invalid auth-parameter error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100