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

Using sistats, sitop, and sitimechart


So far we have used the stats command to populate our summary index. While this works perfectly well, the si* variants have a couple of advantages:

  • The remaining portion of the query does not have to be rewritten. For instance, stats count still works as if you were counting the raw events.

  • stats functions that require more data than what happened in that slice of time will still work. For example, if your time slices each represent an hour, it is not possible to calculate the average value for a day using nothing but the average of each hour. sistats keeps enough information to make this work.

There are a few fairly serious disadvantages to be aware of:

  • The query using the summary index must use a subset of the functions and split fields that were in the original populating query. If the subsequent query strays from what is in the original sistats data, the results may be unexpected and difficult to debug. For example:

    • The following code works fine:

      source...
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