At the time, I thought this app was what I wanted due to confusingly similar app names. I no longer use this and ended up going with the Azure Add-on. If I remember correctly, this app failed even on a fresh instance of Splunk Enterprise. It's also rated quite poorly, it's likely it simply doesn't work. From my brief time developing an app, that error is that an HTTP route doesn't exist. One of two things could be happening: The route doesn't exist. They made a typo in the handler script, web.conf, or restmap.conf. The route exists, but you're denied access. I think Splunk supports this as you need to pass an authentication token. That token should be able to check what permissions you have and deny you appropriately. The response did say Not Found, but sometimes servers will offer that instead of Unauthorized. The response first hits Splunk Web and, if no errors, proceeds to the handler. My guess is it doesn't make it to the handler, and Splunk Web responds with Not Found. Unless someone else knows, it's likely you'll have to debug and fix the script yourself. However, if this is broken, I wonder what else is.
... View more