Installation is as standard for a Splunk app
1 - After running a search, open the SPL Rehab app
2 - Select a search from the User Searches dashboard. Where possible, please ensure you do so using the REST view (Loaded by default)
3 - You will be taken to the Rehab dashboard within the app the search was originally executed. The search will then be automatically executed for you using the start and end times originally used
Before any info is displayed on the Rehab dashboard, a control search is executed to generate all the performance figures. Only when this is completed will the dashboard start to show any true sign of activity.
The dashboard can be broken into two halves. The top half shows the overall stats such as result count, timechart, and fieldsummary as well as performance stats like EPS, total duration, the Lispy, and command count.
The bottom half focusses around stepping through a search. This starts with a table displaying each search statement. Selecting a row will then display the same stats as is possible for the top half but only for a search executed up to the statement selected. Simply put, it enables you to debug your search.
There are two custom scripts packaged within the app. These are responsible for breaking out the search into statement-by-statement chunks.
Most of the objects within the app (4/6) need to be globally shared in order to be able to fully utilize the app. The reason for this is to enable the rehab dashboard to run within the app the original search was executed. This is so the dashboard can use knowledge objects shared at app level and therefore provide a replicated environment in which the search was originally executed
The rehab dashboard has a number of searches built into it in order to function. However its worthwhile bearing in mind that these are all ad-hoc and only a maximum of 6 searches will be executed at any one time due to token suppression. Best practises such as the use of base searches have been used extensively to aid in producing a performant application.
A couple of dashboarding tricks have been used to simplify logic behind the scenes. The main one being the use of hidden text fields. For a simpler example of this use, check out this great solution here
The pipeline for new features can be seen in trello here. Communications, feedback and support can be accessed via the #spl-rehab slack channel in splunkusergroups.slack.com. Opportunities to have your say on which features you would like to see will be available in there!
Converging Data are a Splunk specialist partner. We developed this application to assist our customers maximise the productivity of their environment by helping to eliminate poorly written searches. Our Splunk architects have a wealth of experience in delivering Splunk Professional Services, specialising in delivering tailored solutions specific to individual needs.
If you would like explore how we can better enhance your Splunk environment please get in touch at https://convergingdata.com
- Show runtime per command
- Line chart of runtime per command overlaid with total results
- Time Chart of Search.log
Add result counter to command breakdown table
Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.