The Admin Pilot for Splunk (AP4S) is a comprehensive tool designed to enhance the management and operational efficiency of Splunk environments. AP4S offers detailed tracking and analysis across various facets of Splunk usage and performance, utilizing advanced machine learning techniques to forecast future licensing needs. This powerful app is essential for any Splunk administrator aiming to optimize their implementation and gain deeper insights into their data.
AP4S leverages machine learning to predict future license ingestion, enabling proactive management of licensing costs. It also stores valuable data for long-term analysis, facilitating continuous benchmarking of the Splunk journey.
AP4S is perfect for Splunk administrators who seek to:
- Thoroughly dissect any Splunk implementation.
- Conduct deep dive search analyses with extensive enrichments.
- Simplify scheduled search skip analyses in both SHC and non-SHC environments.
By equipping Splunk administrators with detailed insights and predictive analytics, the Admin Pilot for Splunk (AP4S) is an indispensable tool for maximizing the value of Splunk environments. Try AP4S today to revolutionize your Splunk administration and unlock the full potential of your data.
Cloud & On-Prem:
Please install the following Apps on the same Cloud Search Head or Search Head Cluster you are intending to install and use Admin Pilot for Splunk (AP4S):
1. Splunk App for Lookup File Editing
2.Splunk Machine Learning Toolkit
Please note that you must install the Python for Scientific Computing Add-on before installing the Machine Learning Toolkit. Please download and install the appropriate version here:
- Mac: https://splunkbase.splunk.com/app/2881/
- Linux 64-bit: https://splunkbase.splunk.com/app/2882/
- Windows 64-bit: https://splunkbase.splunk.com/app/2883/
On-Prem:
The On-Prem Monitoring Console must be able to:
1. Search all production indexer clusters (customer may have more than one).
2. Configured to monitor all search heads (all stand alone and search head cluster members)
3. Configured to monitor all heavy forwarders (optional) - These should be configured as the Indexer role to ensure that index pipeline queues are visible. Note: You can deploy the Admin Pilot for Splunk (AP4S) for DS & HF to the DS’s & HFs.
4. Any Splunk Enterprise instance in the customer environment should ideally be configured to show in the Monitoring Console
Cloud:
Install the Admin Pilot for Splunk (AP4S) on the search head cluster and all standalone search heads.
On-Prem:
Installation should be done on a dedicated Search Head for the entire enterprise.
Customers should have existing Monitoring Console in place and configured, if not, configure a standalone search head as a Splunk Monitoring Console according to best practices and then proceed by configuring the dedicated Admin Pilot for Splunk (AP4S) SH.
Admin Pilot for Splunk (AP4S) Index Creation:
Cloud:
1. Login to any search head or search head cluster and create a new index:
2. Index name: ap4s_summary
3. Searchable Time: 400 Days
4. Additional Storage: None
On-Prem:
1. Login to the cluster manager and create a new index:
2. Index name: ap4s_summary
3. Searchable Time: 400 Days
Note for On-Prem customers:
If you have multiple Splunk environments that are separated physically and have its own dedicated Splunk Monitoring Console, Splunk Cluster Manager etc.., you can create a dedicated index for each using this example:
Env1: ap4s_summary_env1
Env2: ap4s_summary_env2
This will keep the data isolated at first and on the Admin Pilot for Splunk (AP4S) enterprise Search Head, all of the data from all of the summary indexes will be combined.
Please be sure to use the naming convention in Appendix C - Monitoring Console Custom Groups Naming Convention
Admin Pilot for Splunk (AP4S) Data Collection Configuration
Got to https://splunkbase.splunk.com/app/6489 and watch this video: https://youtu.be/fvU-uNh1huY also, scroll to find the Admin Pilot for Splunk (AP4S) for Splunk Setup Screen screenshot.
Restore the Admin Pilot for Splunk (AP4S) 101 KV Store Database
watch this video: https://youtu.be/fvU-uNh1huY
Setup the App identities
• Launch AP4S Setup and click on the Admin Pilot for Splunk (AP4S) Custom Identities Gen Job hyperlink.
• The template job called splunk_identities_custom_kv_store_lookup_gen you can use to map your identity fields to Admin Pilot for Splunk (AP4S) identities to help us expose how the various LOBs/SubLOBs, departments etc.. are using Splunk.
• The Most critical fields are: identity, emp_name, emp_type, emp_status, emp_title, emp_dep, emp_lob1, emp_city, emp_region1 & emp_country.
splunk_rest_data_inputs_http_sh_summary_data_gen) now encrypts the HEC token using MD5. This ensures that the HEC token is not exposed in clear text.splunk_internal_splunkd_ui_access_ko_changes_idx_summary_tracker) has received a bug fix, enhancing its performance and reliability.As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.