We're using Opsgenie with Splunk https://splunkbase.splunk.com/app/3759 Splunk Enterprise Version:8.2.9 Installed the app and then added the API (from the Splunk integration in Opsgenie) in the Set up. Have you reviewed the Opsgenie logs to confirm whether or not the alert was received from Splunk? It may have been received, but failed to create an alert for some other reason.   ... View more

Opened a new case with support as this has reoccurred even after upgrading to 7.0. ... View more

The timestamp shown in the error I posted is directly from the splunkd.log file. ... View more

We opened up a case for this bug and was told that there is a slated fix in the next release (6.6.4). ... View more

It has happened again today and our SHC is version 6.6.2 now. Has anyone found a cause and permanent solution to this issue? A rolling restart will temporarily resolve the issue and we don't have the luxury to do a fresh install. Something else that I checked this time was the debug info for each of the individual search heads: http://SearchHeadName/en-US/debug/echo?ping=ok All but one of the search heads were showing UNKNOWN_VERSION listed in the "Server Info" at the bottom of the debug window. I logged into each one individually as the admin account using their respective URLs (http://SearchHeadName/en-US/account/login?loginType=Splunk) and then reloaded the debug URL, and this time the correct version was displayed in the Server Info. After I finished logging into each one, I logged back into the URL for the SHC and this time the correct version was shown. If anyone else has any info on this then please share. Thanks! ... View more