I feel I've missed something obvious here, but can't figure out what:
Anyone?
Solution; The user was not using the search & reporting app and was using a custom built app by a Splunk supplier.
Dashboards behave as normal once search & reporting is used.
Solution; The user was not using the search & reporting app and was using a custom built app by a Splunk supplier.
Dashboards behave as normal once search & reporting is used.
Thanks for pointing me in the right direction, Mark.
No problem, always happy to help 🙂 (Where I can anyway 😛 )
What version of Splunk are you using?
Ah.. tnx, should've added that: 6.2
Post updated.
I take it this is the standard search & reporting app?
If so can you post some screenshots of when you created the dashboard and re-produce the steps so that we can see any mistakes that may have been made.
Thanks
And..... there you have it!
It is not in the default search and reporting app. It's a custom app that our local Splunk supplier set up for us, to keep all our common / custom searches in.
I tried it in the default app now, and it behaves like expected there.
Then my question changes to: why is this behaviour different in the app?
While reading the about dashboards in the manual, I didn't see anything that pointed me in direction of understanding this. I suppose I need to read up more on custom apps....
I'm not 100% sure what your custom app is expected to do, but I'll create an answer so you can accept it so that others know for the future.
don't forget to vote up
Well.. it's not supposed to do too much. It's simply another, standard search app, but it's there to serve as placeholder for searches and reports that are published for everyone.
It's just a housekeeping / access control structure thing, really.