Implementing Splunk 7, Third Edition

Implementing Splunk 7, Third Edition - Third Edition

Overview of this book

Splunk is the leading platform that fosters an efficient methodology and delivers ways to search, monitor, and analyze growing amounts of big data. This book will allow you to implement new services and utilize them to quickly and efficiently process machine-generated big data. We introduce you to all the new features, improvements, and offerings of Splunk 7. We cover the new modules of Splunk: Splunk Cloud and the Machine Learning Toolkit to ease data usage. Furthermore, you will learn to use search terms effectively with Boolean and grouping operators. You will learn not only how to modify your search to make your searches fast but also how to use wildcards efficiently. Later you will learn how to use stats to aggregate values, a chart to turn data, and a time chart to show values over time; you'll also work with fields and chart enhancements and learn how to create a data model with faster data model acceleration. Once this is done, you will learn about XML Dashboards, working with apps, building advanced dashboards, configuring and extending Splunk, advanced deployments, and more. Finally, we teach you how to use the Machine Learning Toolkit and best practices and tips to help you implement Splunk services effectively and efficiently. By the end of this book, you will have learned about the Splunk software as a whole and implemented Splunk services in your tasks at projects

Title Page

Packt Upsell

Contributors

Preface

Free Chapter

The Splunk Interface

Logging in to Splunk

The home app

The top bar

The Search & Reporting app

Using the time picker

Using the field picker

The top bar in Splunk Cloud

Splunk reference app – PAS

Universal forwarder

eventgen

Next steps

Summary

Understanding Search

Using search terms effectively

Boolean and grouping operators

Clicking to modify your search

Using fields to search

Using wildcards efficiently

All about time

Making searches faster

Sharing results with others

Searching job settings

Saving searches for reuse

Creating alerts from searches

Event annotations

Summary

Tables, Charts, and Fields

About the pipe symbol

Using top to show common field values

Using stats to aggregate values

Using chart to turn data

Using timechart to show values over time

Working with fields

Chart enhancements in version 7.0

Summary

Data Models and Pivots

What is a data model?

What does a data model search?

Acceleration in version 7.0

Creating a data model

Summary

Simple XML Dashboards

The purpose of dashboards

Using wizards to build dashboards

Converting the panel to a report

Back to the dashboard

Scheduling the generation of dashboards

Summary

Advanced Search Examples

Using subsearches to find loosely related events

Using transaction

Determining concurrency

Calculating events per slice of time

Rebuilding top

Acceleration

Version 7.0 advancements in metrics

Summary

Extending Search

Using tags to simplify search

Using event types to categorize results

Using lookups to enrich data

Using macros to reuse logic

Creating workflow actions

Using external commands

Summary

Working with Apps

Defining an app

Included apps

Installing apps

Building your first app

Editing navigation

Customizing the appearance of your app

Object permissions

App directory structure

Self-service app management

Summary

Building Advanced Dashboards

Reasons for working with advanced XML

Reasons for not working with advanced XML

Development process

Advanced XML structure

Converting simple XML to advanced XML

Module logic flow

Understanding layoutPanel

Reusing a query

Using intentions

Creating a custom drilldown

Third-party add-ons

Summary

Summary Indexes and CSV Files

Understanding summary indexes

When to use a summary index

When to not use a summary index

Populating summary indexes with saved searches

Using summary index events in a query

Using sistats, sitop, and sitimechart

How latency affects summary queries

How and when to backfill summary data

Reducing summary index size

Calculating top for a large time frame

Using CSV files to store transient data

Summary

Configuring Splunk

Locating Splunk configuration files

The structure of a Splunk configuration file

The configuration merging logic

An overview of Splunk.conf files

User interface resources

Summary

Advanced Deployments

Planning your installation

Splunk instance types

Common data sources

Sizing indexers

Planning redundancy

Working with multiple indexes

Deploying the Splunk binary

Using apps to organize configuration

Configuration distribution

Using LDAP for authentication

Using single sign-on

Load balancers and Splunk

Multiple search heads

Summary

Extending Splunk

Writing a scripted input to gather data

Using Splunk from the command line

Querying Splunk via REST

Writing commands

Writing a scripted lookup to enrich data

Writing an event renderer

Writing a scripted alert action to process results

Hunk

Summary

Machine Learning Toolkit

What is machine learning?

Defining the toolkit

The toolkit workbench

Assistants

Extended SPL (search processing language)

Building a model

Validation

Summary

Index

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Using transaction

The transaction command lets you group events based on their proximity to other events. This proximity is determined either by ranges of time, or by specifying the text contained in the first and/or last event in a transaction.

This is an expensive process, but is sometimes the best way to group certain events. Unlike other transforming commands, when using transaction, the original events are maintained, and are grouped together into multivalued events.

Some rules of thumb for the usage of transaction are as follows:

If the question can be answered using stats (and it often can), it will almost always be more efficient.
All the events needed for the transaction have to be found in one search.
When grouping is based on field values, and all the events need at least one field in common with at least one other event, then it can be considered as part of the transaction. This doesn't mean that every event must have the same field, but that all events should have some field from...

Implementing Splunk 7, Third Edition - Third Edition

Implementing Splunk 7, Third Edition - Third Edition

Overview of this book

Related Content you might be interested in

Current Title:

Implementing Splunk 7, Third Edition - Third Edition

Splunk 7.x Quick Start Guide

Mastering Splunk 8

Splunk 7 Essentials

Using transaction