Issue Summary
If this plugin is installed to the Alerta side, Zabbix can't send resolved alerts for the triggers that have manual closing disabled. Alerta returns "Zabbix API doesn't allow manual closing"
Environment
OS: [Ubuntu 18.04] Docker
API version: 7.4.5-8.0.1
Deployment: Docker
For self-hosted, WSGI environment: [eg. nginx/uwsgi, apache/mod_wsgi]
Database: Postgres
Server config:
Auth enabled? No
Auth provider? Basic
Customer views? No
To Reproduce
Steps to reproduce the behavior:
Create a dummy trigger in Zabbix without manual closing enabled. Do install Zabbix plugin on Alerta.
Click on the ack button and don't select manual close from the update problem page.
Change the threshold or trigger to auto-close the trigger. See if it succeeds.
See the error.
/
ERROR: ('Zabbix: ERROR - %s', ZabbixAPIException('Error -32500: Application error., Cannot close problem: trigger does not allow manual closing.', -32500))
Aborted!
/
Expected behavior
Alerta plugin shouldn't try to go back and update the problem on Zabbix when receiving a resolved alert from Zabbix unless the user clicks the close or the ack button.
Explanation
Our configuration is like this if it's helpful
Zabbix -> Customer-Alerta(7.4.5)(Doesn't have this plugin) ->(Forward Plugin/Not Federated) -> Central Alerta(8.0.1)(Has this plugin)
So in order to solve this problem we've removed the Zabbix plugin from Customer Alerta but kept it on the Central Alerta, alerts do come after this. But we can't send an update from Central Alerta even if we add "attributes.zabbixUrl" to the alert.
Issue Summary If this plugin is installed to the Alerta side, Zabbix can't send resolved alerts for the triggers that have manual closing disabled. Alerta returns "Zabbix API doesn't allow manual closing"
Environment
OS: [Ubuntu 18.04] Docker
API version: 7.4.5-8.0.1
Deployment: Docker
For self-hosted, WSGI environment: [eg. nginx/uwsgi, apache/mod_wsgi]
Database: Postgres
Server config: Auth enabled? No Auth provider? Basic Customer views? No
To Reproduce Steps to reproduce the behavior:
/ ERROR: ('Zabbix: ERROR - %s', ZabbixAPIException('Error -32500: Application error., Cannot close problem: trigger does not allow manual closing.', -32500)) Aborted! /
![image](https://user-images.githubusercontent.com/49399656/101185293-be293a80-3662-11eb-91d6-bc70ef846091.png)
Expected behavior Alerta plugin shouldn't try to go back and update the problem on Zabbix when receiving a resolved alert from Zabbix unless the user clicks the close or the ack button.
Explanation
Our configuration is like this if it's helpful
Zabbix -> Customer-Alerta(7.4.5)(Doesn't have this plugin) ->(Forward Plugin/Not Federated) -> Central Alerta(8.0.1)(Has this plugin)
So in order to solve this problem we've removed the Zabbix plugin from Customer Alerta but kept it on the Central Alerta, alerts do come after this. But we can't send an update from Central Alerta even if we add "attributes.zabbixUrl" to the alert.