Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing Splunk: Big Data Reporting and Development for Operational Intelligence

You're reading from   Implementing Splunk: Big Data Reporting and Development for Operational Intelligence Learn to transform your machine data into valuable IT and business insights with this comprehensive and practical tutorial

Arrow left icon
Product type Paperback
Published in Jan 2013
Publisher Packt
ISBN-13 9781849693288
Length 448 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
VINCENT BUMGARNER VINCENT BUMGARNER
Author Profile Icon VINCENT BUMGARNER
VINCENT BUMGARNER
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Implementing Splunk: Big Data Reporting and Development for Operational Intelligence
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. The Splunk Interface FREE CHAPTER 2. Understanding Search 3. Tables, Charts, and Fields 4. Simple XML Dashboards 5. Advanced Search Examples 6. Extending Search 7. Working with Apps 8. Building Advanced Dashboards 9. Summary Indexes and CSV Files 10. Configuring Splunk 11. Advanced Deployments 12. Extending Splunk Index

App directory structure


If you do much beyond building searches and dashboards, sooner or later you will need to edit files in the filesystem directly. All apps live in $SPLUNK_HOME/etc/apps/. On Unix systems, the default installation directory is /opt/splunk. On Windows, the default installation directory is c:\Program Files\Splunk. This is the value that $SPLUNK_HOME will inherit on startup.

Stepping through the most common directories, we have:

  • appserver: This directory contains files that are served by the Splunk web app. The files that we uploaded in earlier sections of this chapter are stored in appserver/static.

  • bin: This is where command scripts belong. These scripts are then referenced in commands.conf. This is also a common location for scripted inputs to live, though they can live anywhere.

  • default and local: These two directories contain the vast majority of the configurations that make up an app. We will discuss these configurations and how they merge in Chapter 10, Configuring...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image