After disabling integration, the api_key in opsgenie is not deactivated

[Nikita Egorov]

Good afternoon, everyone! The following story happened to me. I use zabbix integration in opsgenie. After I disabled this integration, I kept getting alerts until I disabled the action in Zabbix to send the alert.

Questions:
1. Do I understand correctly that when the integration is disabled, the api_key remains valid and continues to work?
2. If it continues to be valid, then why do I need to turn off integration?

[John M]

Hi @Nikita Egorov ,

The integration should not work after being disabled. You should see a log entry in the debug logs stating that a payload was discarded due to the integration being disabled. 

The easiest way to check would be to search the alert's ID or alias in the debug logs - the first log entry with that value should be the 'create' action which will show you how the alert is being created (which integration and action it's using.

This article gives some examples of how to search the debug logs:

https://community.atlassian.com/t5/Opsgenie-articles/Useful-Opsgenie-debug-log-queries/ba-p/2444507

[Nikita Egorov]

Hi @John M 
Thank you for answer. Unfortunately, I have now looked in more detail using your link as an example. Integration with Zabbix is disabled, I looked at the logs when creating the alert, integration with Zabbix was used, which is disabled. It stopped working only after I turned off action in Zabbix. But this is a shutdown on the part of Zabbix, if the api_key were invalid, we would see a delivery error in Zabbix.

[John M]

Hi @Nikita Egorov ,

Are you certain the integration itself is disabled, and not just the notifications?

If the integration is disabled you will see this:

However, there is a separate option to just disable the notifications:

Additionally, have you verified that the API key in your Zabbix instance is the same one from the disabled Zabbix integration?

If you've checked both of those things, please open a ticket here so our support team can look into it - thanks!

[Nikita Egorov]

My apologies for not responding for a long time. Yes, the api_key is the same, integration has been disabled. Thank you, then I will recreate the problem again in order to write it in more detail in the ticket