After the Conf talk on this app last year, I have finally been able to get around to onboarding more users and a need for the Welcome creator app. I am a little bit confused as to what/how i need to package this to send to Splunk Cloud team for installation, as it has the app itself, the template bits you have to move to another folder and then the customized app you create specifically for your environment.
I have installed the app and followed the instructions to install in a trial version of Splunk enterprise locally.
( install app, stage template, create workspace from template and customize)
Now I have a working customized dashboard I wish to upload to cloud. What parts do I send to the Splunk Cloud support then? I see it as 3 portions.
1. Splunkbase app
2. "Workspace template" $SPLUNKHOME/etc/apps/welcome/static/workspace to $SPLUNKHOME/share/splunk/app_templates/workspace
3. My Customized App
Do i only upload 3 and assign to all sso users as home? or do I need 1&3 uploaded to them and 2. zipped down and instructions on the place I need them to place it?
Thanks for any replies
Thanks so much for your interest and I find your explanation of what you tried to be impressive and thorough. So thanks for making it easy for me to follow.
To be honest, you're suffering from a failure on my (author) part! I haven't finished doing the work to get the app to be Cloud approved. That's really the best approach because as you surmised, the app itself is a collection of shared panels. So without that app, you'd have to clone each panel you want into a new app for Cloud...which is redundant 😞
Oddly enough, this app's lack of Cloud approval has come up a bit this week already (and it's only Tuesday). Perhaps the best thing would be for me to follow through and finally get it approved. That way you would have less complexity and a more scalable solution.
Once this is Cloud approved, you'd want the Welcome Page Creator app deployed and that should include the aspects for the template app. If you customized the template to be more specific to your company, then you'd want to submit that for placement in the templates directory. Then you should be able to provision such new apps as needed from the Splunk Enterprise Cloud Web UI. If you created any new panels, you'd likely want to create your own supplemental app to deliver those to Cloud.
I realize this sounds a bit complicated but I'm hoping that you and I can work through this and I'll use all our learnings to create stronger documentation for future Cloud cool kids like yourself.
Let me pause there and see what questions you have? I've also shared this post with my peers on the Cloud side of the house to keep me honest in case I am inaccurate on any Cloud feature/functionality for this approach.
Thanks for your thorough answer, You both answered my base questions and my next steps question pretty well.
I would imagine once you work on it and get this approved for cloud your instructions will be better laid for future on person cloud n00bs like myself. The one point I am a little bit fuzzy on is that after the "Welcome Page Creator" app is cloud approved and I get it installed via cloud support mechanisms, I would take my "template"/ app created as part of step 4 and bundle THAT one up for Cloud to place in my templates directory? I assume if that is correct then it'll all just fall into place and assign that as the default app for the appropriate users/groups and call it a day?
I don't believe I have any more questions at this time. I was building this as presteps after that SSO-Splunk connection and before we (myself and Splunk team) held lunch training on getting our internal staff trained for basic splunking and official account creation. It's not a huge loss to have to wait on it a little while, just figured a company logo, internal support info, and a few things like that would be more inviting then assigning "search" or "Windows Infrastructure App" as I would guess 95% of IT here have never used such a suite like splunk exactly. This is one of those tools that has no measurable value towards kpi's but I think can help make the first timers experience less jarring to those who expect everything to be candycoated smartphone app. I appreciate your efforts in demonstrating such a usage of panels and onboarding process.
In lieu of a "got burched" button I have no other choice but to mark this as "Accepted Answer"
Hey @tysnider - You're reference to step 4 is perfect. Assuming you created a template that's more appropriate than the one in the app itself then you can ask Cloud to get it added to the templates directory for future app promulgation.
"can help make the first timers experience less jarring to those who expect everything to be candycoated smartphone app." - you nailed it. That's my experience and motivation for this.
"got burched" - Ha ha. Thanks for remembering my slides!