Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Splunk Best Practices
  • Table Of Contents Toc
  • Feedback & Rating feedback
Splunk Best Practices

Splunk Best Practices

By : Travis Marlette
4.8 (5)
close
close
Splunk Best Practices

Splunk Best Practices

4.8 (5)
By: Travis Marlette

Overview of this book

This book will give you an edge over others through insights that will help you in day-to-day instances. When you're working with data from various sources in Splunk and performing analysis on this data, it can be a bit tricky. With this book, you will learn the best practices of working with Splunk. You'll learn about tools and techniques that will ease your life with Splunk, and will ultimately save you time. In some cases, it will adjust your thinking of what Splunk is, and what it can and cannot do. To start with, you'll get to know the best practices to get data into Splunk, analyze data, and package apps for distribution. Next, you'll discover the best practices in logging, operations, knowledge management, searching, and reporting. To finish off, we will teach you how to troubleshoot Splunk searches, as well as deployment, testing, and development with Splunk.
Table of Contents (11 chapters)
close
close

Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "For instance, in Cisco log files there is a src_ip field."

A block of code is set as follows:

[mySourcetype] 
REPORT-fields = myLinuxScript_fields

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

[myUnstructured] 
DATETIME_CONFIG = 
NO_BINARY_CHECK = true 
category = Custom 
pulldown_type = true

Any command-line input or output is written as follows:

ssh -v -p 8089 mydeploymentserver.com

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "The most common messages we see are things like unauthorized login attempt <user> or Connection Timed out to <ip address>."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY