So, the actual problem was that the Okta TA was automatically getting "included" into the ES app, so the nav and views defined in that TA were 'a part of' the ES app. See https://docs.splunk.com/Documentation/ES/5.2.2/Install/ImportCustomApps for information on this feature of ES. By default, any app that starts with "TA-" (and others) is automatically "imported" into the ES app. Since the Okta add-on starts with "TA-" (the name is "TA-Okta_Identity_Cloud_for_Splunk"), it was getting imported and visible in ES, causing the nav issues (and other pages to show up). To fix: 1. In the ES app, navigate to "Configure | General | App Imports Update". 2. Click on the "update_es" item to edit it. 3. Add "|TA-Okta_Identity_Cloud_for_Splunk" to the "Application Exclusion Regular Expression" field. 4. Save your changes. 5. Restart Splunk. ... View more

I'm not sure if this is what you are looking for, but I've been able to modify the JIRA add-on to allow you to connect to multiple different JIRA servers by specifying a "server=XXX" parameter in the commands. E.g: ... | jira server=server1 filters ... Let me know if you are interested in the code changes to do this. ... View more

The only errors I see from that search are ones like these: 2017-10-19 16:53:46,563 INFO [59e910dz8c7f8ca46e80] error: 138 - Masking the original 404 message: 'The path '/en-US/custom/lookup_editor/lookup_edit/get_lookup_backups_list' was not found.' with 'Page not found!' for security reasons I don't see any errors from startup. (NOTE: we deployed the app by dropping it on the Deployer, then pushing it to the SHC. I'm not sure if the SH gets restarted automatically by this process or not.) ... View more

We tried 2.7.0, and got the same results (error). ... View more

I'm getting the same errors. SHC 6.5.1, LFE 2.71. Fresh install of the app into an existing SHC. ... View more