Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't send resolved alerts to Alerta if this plugin is installed. #331

Open
burakksglu opened this issue Dec 4, 2020 · 1 comment
Open
Labels
question Further information is requested

Comments

@burakksglu
Copy link

burakksglu commented Dec 4, 2020

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:

  1. Create a dummy trigger in Zabbix without manual closing enabled. Do install Zabbix plugin on Alerta.
  2. Click on the ack button and don't select manual close from the update problem page.
  3. Change the threshold or trigger to auto-close the trigger. See if it succeeds.
  4. See the error.

/*
ERROR: ('Zabbix: ERROR - %s', ZabbixAPIException('Error -32500: Application error., Cannot close problem: trigger does not allow manual closing.', -32500))
Aborted!
*/
image
image

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.

@satterly satterly added the question Further information is requested label Nov 27, 2021
@lk-eska
Copy link

lk-eska commented Jan 6, 2022

can we do anything for this? It shouldn't try to close it back in zabbix if the close is coming from zabbix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: 📝 Todo
Development

No branches or pull requests

3 participants