All Apps and Add-ons

Add navigation to a Splunk app

francisc
Engager

I've added a new view name by editing the default.xml via Splunk Web as an admin, restarted Splunk after and refreshed the instance using /debug/refresh but the new view name is not being added. Is there something i need to do i am missing?

0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

@francisc - Even you don't need to do debug refresh when you change it from Splunk web.
Just make sure for App you are updating nav in that App only you are checking the navigation.
Make sure navigation permission/visibility is "Only in this App".
By looking at your xml content here, just make sure you have <nav> as root tag in your xml.

francisc
Engager

@VatsalJagani, i did a test using my dev box using a test_app which has the nav tag and i am getting the same results. Sharing is app and permissions are read for everyone and write for admin.

0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

I'm afraid then it should work. Just to make sure that you are not getting any error while saving the navigation.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Looks correct to me, the view should appear in the account control collection for users that can see the view.

0 Karma

francisc
Engager

@martin_mueller, where do you configure users to see the views.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Which view did you add? Did you make sure the view id is spelled correctly?

0 Karma

francisc
Engager

Yes i followed the one on top,

view name changed is user_group_changes from the xml

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Post your navigation XML, and make sure the view id is spelled correctly.

0 Karma

francisc
Engager
<view name="flashtimeline" />
<collection label="Splunk health">
    <view name="license_usage" />
    <view name="data_inputs_health" />
</collection>
<collection label="Access">
    <view name="authentication_summary" default='true' />
    <view name="hp-ux_authentication" />
    <view name="hp-ux_sudo" />
    <view name="aix_authentication" />
    <view name="aix_sudo" />
</collection>
<collection label="Account control">
    <view name="user_account_changes" />
    <view name="user_group_changes" />
</collection>
<collection label="Auditing">
    <view name="cron_jobs" />
    <view name="ssh_non_interactive_commands" />
    <view name="windows_file_audit" />
</collection>
<collection label="Reports">
<collection label="User Audit">
    <collection label="HP-UX">
  <saved source="unclassified" match="HPux_report" />
    </collection>
    <collection label="AIX">
  <saved source="unclassified" match="AIX_report" />
    </collection>
    <collection label="Windows">
       <view name="report1" />
       <view name="report2" />
       <view name="report3" />
       <view name="report4" />
    </collection>
</collection>

<collection label="Searches">
<collection label="**">
  <saved source="unclassified" match="Syslog" />
</collection>
</collection>    

The view that i have added is user_group_changes which is not showing on the dashboard.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...