Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
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

Product type Book
Published in Jan 2013
Publisher Packt
ISBN-13 9781849693288
Pages 448 pages
Edition 1st Edition
Languages
Concepts
Author (1):
VINCENT BUMGARNER VINCENT BUMGARNER
Profile icon VINCENT BUMGARNER

Table of Contents (19) Chapters

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 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 event types to categorize results


An event type is essentially a simple search definition, with no pipes or commands. To define an event type, first make a search. Let's search for:

sourcetype="impl_splunk_gen" logger="AuthClass"

Let's say these events are login events. To make an event type, choose Event type... from the Create menu, as shown here:

This presents us with a dialog, where we can assign a Name string and optionally any Tags(s) to this event type, as shown in the following screenshot:

Let's name our event type login.

We can now search for the same events using the event type:

eventtype=login

Event types can be used as part of another search, as follows:

eventtype=login loglevel=error

Event type definitions can also refer to other event types. For example, let's assume that all login events that have a loglevel value of ERROR are in fact failed logins.

We can now save this into another event type using the same steps as mentioned previously. Let's call it failed_login. We can now...

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 €14.99/month. Cancel anytime}