Book Image

Splunk 9.x Enterprise Certified Admin Guide

By : Srikanth Yarlagadda
Book Image

Splunk 9.x Enterprise Certified Admin Guide

By: Srikanth Yarlagadda

Overview of this book

The IT sector's appetite for Splunk and skilled Splunk developers continues to surge, offering more opportunities for developers with each passing decade. If you want to enhance your career as a Splunk Enterprise administrator, then Splunk 9.x Enterprise Certified Admin Guide will not only aid you in excelling on your exam but also pave the way for a successful career. You’ll begin with an overview of Splunk Enterprise, including installation, license management, user management, and forwarder management. Additionally, you’ll delve into indexes management, including the creation and management of indexes used to store data in Splunk. You’ll also uncover config files, which are used to configure various settings and components in Splunk. As you advance, you’ll explore data administration, including data inputs, which are used to collect data from various sources, such as log files, network protocols (TCP/UDP), APIs, and agentless inputs (HEC). You’ll also discover search-time and index-time field extraction, used to create reports and visualizations, and help make the data in Splunk more searchable and accessible. The self-assessment questions and answers at the end of each chapter will help you gauge your understanding. By the end of this book, you’ll be well versed in all the topics required to pass the Splunk Enterprise Admin exam and use Splunk features effectively.
Table of Contents (17 chapters)
Part 1: Splunk System Administration
Part 2:Splunk Data Administration
Chapter 12: Self-Assessment Mock Exam

Troubleshooting conf files using the btool command

As we have seen, conf files can be placed in more than one place, and in some cases, the default conf setting might need to undergo changes, which an administrator or Splunk user will create in /local directories, either in an etc/apps/<app_name> or users/<user_name>/<app_name> directory.

As more conf files are added to or updated, it becomes very difficult to track the changes to troubleshoot Splunk issues. In this situation, the btool CLI command is very helpful for seeing merged versions of conf files that exist on disk. Let’s look at the syntax of the btool command. It must be issued from the $SPLUNK_HOME/bin directory:

./splunk btool  <conf_file_prefix> [list|layer|add|delete]  --debug --app=<app_name> --user=<user_name>

Let’s understand the components:

  • --debug: This option shows the absolute path of the conf file’s location in the system...