I've developed a custom splunk application and I'm seeing some extremely unexpected behavior with the application.
I've installed this application under three different Splunk instances in my development environment. It works fine with no issues.
Now when installed in the production servers, the application does not work. Specifically, the menu does not show up. The default.xml file exists and is accurate, the views exist and are accurate as well.
I'm seeing the following error in the error logs
WARNING [4ed920a766175a9bd0] view:397 - An unknown view name "View-4" is referenced in the navigation definition for "myapp".
What could be the problem?
TIA.
In your default.xml you apparently have a reference to View-4. Literally you should just need to remove that reference, alternatively it could be a permissions option on a view.
Most of these sorts of errors are people encountering silly errors on their test setups, they fix them but then completely forget about these small fixes when the app is deployed.
This is most likely because you have created or made a change to a view using the UI and not made it public. This means it is hidden in your etc/users/usernme/appname/local/data/ui/views folder. If you see View-4.xml there, copy it into a view folder in your app directory.
You don't need to award points as well unless you feel its a really really good answer. Basically you want to tick to accept an answer so its identified as helpful. Above the tick you will see two arrows and a zero. If you click on the arrow up it will award the person bonus points, this method doesn't cost you points. If you award points it gives your points to them
Where does the points awarded come to play? Should I be granting points per answer?
Also, if you have a look through your past questions you have looooaads that haven't got an accepted answer, do the community a favor and accept all the questions that have helped - this improves the quality of search results if someone finds one of your questions 🙂
In your default.xml you apparently have a reference to View-4. Literally you should just need to remove that reference, alternatively it could be a permissions option on a view.
Most of these sorts of errors are people encountering silly errors on their test setups, they fix them but then completely forget about these small fixes when the app is deployed.