Splunk Cloud stops sending Splunk alerts to Opsgenie if Google Workspace or Jamf Pro add ons are enabled

Issue Summary

User is reprorting that they were using Opsgenie plugin for Splunk Cloud to send Splunk alerts to Opsgenie. After several months of operation it suddenly stopped working - it stopped sending any alerts to Opsgenie. They didn't change any configurations or run any upgrades that could cause that.

The error in Splunk is _internal index that started occurring at the time the plugin broke: action=opsgenie STDERR - Unexpected error: No credentials found. Could not get Opsgenie API Key.

Splunk Support don't support external plugins, and they redirected tje user to Opsgenie Support.

In the following thread in Splunk Answers: https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-fix-Opsgenie-setup-errors/m-p/643270#M79137
Several other people complained there about exact same error.

User followed one of the suggestions there and tried disabling other Splunk plugins. In their case it was Splunk Add-on for Google Workspace causing issue.

In the user case it turned out it was Jamf Pro Add-on -

After they disabled it Opsgenie plugin started to work, and the mentioned error above went away.

This is a temporary workaround, but eventually they will need both.

Steps to Reproduce

1. Use Opsgenie Plugin in Splunk, as per documentation

Expected Results

1. It should work with other plugins as well.

Actual Results

1. Error _internal index that started occurring at the time the plugin broke: action=opsgenie STDERR - Unexpected error: No credentials found. Could not get Opsgenie API Key.

Workaround

Disabling the other plugin that is interfering with Opsgenie